Clinical data and interoperability
What the current application stores, and where an external integration needs separate validation.
Clinical records in Curenium
The application has routes and data models for patients, encounters, orders, results, and imaging-study metadata. Those internal records do not, on their own, establish a general HL7 v2, FHIR R4, or DICOM exchange interface.
Patient records
How patient and encounter information is organized in the EHR.
Imaging workflow
Ordering, study metadata, and reporting in the current product.
External standards
HL7, FHIR, and DICOM are important healthcare interoperability standards. Curenium has some integration-specific code, including an NHS personal-demographics FHIR request path and imaging-study metadata. That is narrower than a general two-way EHR interface or certified DICOM conformance.
Confirm the specific exchange format, direction, endpoint, authentication method, environment, and acceptance tests with the Curenium team. Do not assume that a standards-based connection is active for your organization simply because a standard is described here.