AuroraMed v0.5.0 is a synthetic-data pilot. See exactly what's built →

Product tour

FHIR and HL7 (simulated)

A read-only FHIR interface and HL7 admit, discharge and transfer messages. Both are simulated.

Interoperability in the pilotThe hub exposes a read-only FHIR R4-style interface, sends HL7 ADT messages to an in-process simulated partner, and validates inbound messages without applying them.FHIR R4-styleread-only server(simulated)HL7 ADT outA01, A03, A04, A08to a simulated partnerInbound HL7:validate only,nothing appliedReal partnersystemsnot connectedIn the pilotDesigned, not builtSimulatedDecision / caution

Diagram: interoperability. Nothing leaves the hub for a real outside system.

What exists Simulated

  • A read-only FHIR R4-style interface with a capability statement, patient, allergy, medication request, condition, observation and appointment resources, and a patient-everything view.
  • HL7 v2 ADT admit, discharge, registration and update messages sent to an in-process simulated partner.
  • Inbound messages are parsed and validated and reported as not applied.
  • A fix for message escaping was made and tested.

Not built Designed

  • No connection to a real partner, HIE or registry.
  • No FHIR write, no C-CDA and no DICOM.
  • No interface engine.
  • No claim of conformance with any certification program.

Common questions

Does AuroraMed support FHIR?
It has a read-only FHIR R4-style interface that is simulated: it answers requests from inside the hub, and no partner has connected to it. We make no conformance claim.

See fhir and hl7 (simulated) on synthetic data

A short walkthrough. No patient information needed.

See the synthetic-data demo first.Request a demo