Medical & Healthcare ERP.

What is ETHX Softcon Medical & Healthcare ERP on Oracle?

ETHX Softcon Medical & Healthcare ERP is a set of healthcare-specific extensions on Oracle ERP for hospitals, clinics, and medical device firms, covering patient data connectors, clinical supply chain, HR credentialing, medical billing, and regulatory reporting. It does not replace an EHR; instead it integrates with clinical systems through HL7 and FHIR connectors and Oracle Health interoperability APIs, while Oracle handles supply chain, HR, finance, and billing. Clinical supply chain features include lot and expiry control, chain-of-custody, recall, and par-level replenishment.

On Oracle HCM Cloud, it tracks licences, certifications, and CPD with credential expiry alerts. Medical billing covers insurance, co-pay, and claims, integrated with Fusion Financials AR. Regulatory reporting supports FDA, HIPAA, and MDR requirements with an audit trail. Data handling is HIPAA-aware, with PII redaction and access controls. ETHX Softcon delivers through assessment, design, build, compliance validation, and a run phase that includes hypercare and managed support.

What should you evaluate before extending Oracle ERP for healthcare operations?

The first question is where the boundary sits between clinical and business systems. The electronic health record should remain the clinical record, while the ERP handles supply chain, workforce and finance, and only the data each side genuinely needs should cross between them. HL7 FHIR is a standard for exchanging healthcare information electronically, organised into defined resources, and many hospitals also still run older HL7 version 2 interfaces. Knowing which standard each source system supports, and which patient identifiers must move, shapes both the integration effort and the compliance scope.

Wherever an ERP extension stores or processes electronic protected health information, for example in patient billing or case-level supply usage, US organisations fall under the HIPAA Security Rule. Its technical safeguards cover access control, audit controls, integrity, person or entity authentication and transmission security, and NIST SP 800-66 gives practical guidance on implementing the rule. Ask how each safeguard is met in the extension, who reviews the audit logs, and what contractual arrangements, such as business associate agreements, cover any vendor that handles this data. Organisations outside the US will have their own privacy and medical device rules to map in the same way.

Operational requirements matter as much as compliance. Clinical supply chains need lot and expiry tracking that can trace a recalled item to where it was used, and credentialing needs reliable expiry alerts for licences. Clinicians have little tolerance for double entry, so capture data once at the point of care or receipt and pass it on, and validate each release against documented test evidence before go-live.