Interoperability and standards
Integration status
Every external connector is simulated or absent in the pilot.
How to read status labels: In the pilot (v0.5.0, synthetic data) Simulated in the pilot (no real external system) Designed, not yet built Open decision Not offered / no claim made Planned partner integration
C0319Does AuroraMed connect to outside systems today?
No. The pilot has no connection to any real outside system. Laboratory, imaging, pharmacy, prescription-monitoring, clearinghouse and HL7 or FHIR partners are all simulators inside the hub, run with synthetic data, so what you see is a simulation of a feed, not a real one.
C0320Does AuroraMed support HL7 v2?
In simulation only. The pilot builds and parses HL7 v2 order and result messages for a simulated lab, and sends ADT admit, discharge, registration and update messages to an in-process simulated partner. Inbound messages are validated and not applied. No real partner is connected, and the interface engine is not built.
C0321Does AuroraMed support FHIR?
In simulation only. The pilot has a read-only FHIR R4-style interface (capability statement, patient, allergy, medication request, condition, observation, appointment and a patient-everything view) that answers inside the hub. No partner is connected, writes are refused, and listing a standard is not a claim of conformance. Bulk export and subscriptions are not built.
C0322Is SMART on FHIR supported?
No. SMART App Launch is a design target for the FHIR interface and is not implemented. The pilot's FHIR-style interface is read-only and simulated.
C0323Can AuroraMed exchange C-CDA documents?
C-CDA exchange is planned for transitions of care. It is not built, and no conformance is claimed.
C0324Does AuroraMed support DICOM imaging?
No. DICOM, PACS and RIS functions are designed, with an on-site image store. The pilot has imaging orders and simulated report ingestion with an impression and a critical-finding flag, and no images.
C0325Can AuroraMed connect to laboratory analyzers?
No. Analyzer and middleware connections are designed and not built. The pilot has a simulated reference-lab connector that exchanges HL7 v2 messages inside the hub.
C0326Does AuroraMed support e-prescribing?
In simulation only. The pilot walks the whole flow with synthetic data: draft, sign and send by the named prescriber, a simulated pharmacy network, pharmacist verify, clarify or reject, dispense, cancel and refill decisions. Controlled substances need a password step-up and a simulated monitoring check. It is not DEA EPCS, no real pharmacy is connected, and it needs external certification time before any real use.
C0327Can claims go to a clearinghouse?
Only a simulated one. The pilot builds and scrubs claims, sends them to a simulated clearinghouse inside the hub, and handles acknowledgements, remittances and denials with synthetic fee schedules and code sets. No clearinghouse partner has been chosen and no real claim has been sent.
C0328Are payer eligibility checks available?
Only simulated. The pilot stores simulated 270/271-style eligibility results with expiry and re-verification. No payer is connected and no partner has been chosen.
C0329Is TEFCA supported?
TEFCA and national exchange networks such as Carequality and CommonWell are planned. Participation path is an open decision and nothing is connected.
C0330Can AuroraMed join a health information exchange?
Exchange participation is planned. No exchange agreement exists.
C0331Which standards versions will be used?
The specification pins confirmed versions and marks others for verification. Version pinning is a configuration release rather than a code change. Nothing is a claim of conformance.
C0332Is Direct messaging supported?
Direct secure messaging is on the planned interoperability list, not built.
C0333Are public-health reports supported?
Immunization registry, electronic lab reporting, syndromic surveillance and registry exports are designed interfaces, all off by default, none built.
C0334How will an outside interface be secured?
All interfaces terminate at the on-site engine, use mutual TLS, scoped service identities, per-channel rate limits and dead-letter queues, and audit a hash of each message. Design only.
C0335Can a partner flood the interface engine?
Per-channel bulkheads, rate limits and dead-letter queues are designed so one partner's bad traffic cannot starve others.
C0336Will device data reach the chart?
Bedside monitors, scales, pumps and analyzers connect through a device gateway in the design, read-only by default for infusion pumps and ventilators. Not built.
C0337Will pumps be controlled by AuroraMed?
No. Write-back to infusion pumps is off unless a clinical safety case and vendor certification exist. That policy is an open item.
C0338Are barcode scanners supported?
Bedside scanning with allow-listed scanners is designed. Not built.
C0339Do wearables feed the record?
Patient-generated device data is a planned, low-priority feature flagged by source, not built.
C0340Can AuroraMed send SMS alerts?
No. SMS, pager and overhead paging are not built. The design keeps message text free of patient data if a customer allows such gateways, which is off by default.
C0341What terminology sets are bundled?
ICD-10-CM (a curated subset), RxNorm (a subset of common ingredients and drugs), immunization codes CVX (complete as of 2026-09-30), a small allergen set and fifty LOINC codes. SNOMED CT and CPT are not bundled because they need licences.
C0342Will AuroraMed license SNOMED CT and CPT?
Open. Licensing is required and undecided, so those code sets are not included.
C0343Does AuroraMed check drug interactions with a knowledge base?
No licensed one. The pilot's decision support runs against a small synthetic rule table (about 40 drugs and 12 interactions) and is not a clinical knowledge base. Drug knowledge bases are licensed content, and the licence is an open decision.
C0344Can we use our own code sets?
The design supports terminology management with version pinning and mapping, plus a licence register that blocks licensed content without a record. Not built.
C0345Does AuroraMed support country-specific payer formats?
Adapters named in the design include Brazilian TISS, Colombian RIPS, Mexican CFDI and others, loaded as signed plug-ins. None is built.
C0346What partner formats come first?
Country adapter build order and partner endpoints are an open decision.
C0347Will a public API be offered?
Versioned, rate-limited, audited APIs with developer documentation are designed. No public API exists.
C0348Can third-party apps connect to a patient's record?
Through a patient-access FHIR API with patient-scoped tokens in the design, with no bulk export. Not built.
C0349Do interfaces carry full patient data?
Only what the policy allows: each outbound message passes the policy engine and restricted compartments are filtered unless consent is active.
C0350What if the network to a partner is down?
Outbound messages queue persistently and drain in order later; clinical use is unaffected. Designed, not built.
C0351Which ONC certification criteria will apply?
Undecided. Whether AuroraMed seeks US certification is an open item; the design follows certain criteria without claiming any certification.
C0352Is AuroraMed ONC certified?
No. No certification has been sought or earned.