Integration status

C0319Does AuroraMed connect to outside systems today?

No. The pilot has no external connectors of any kind. Lab and imaging results enter through an internal programming interface used by authorized synthetic roles, which is a simulation of a feed, not a real one.

C0320Does AuroraMed support HL7 v2?

HL7 v2 interfaces are designed, including ADT, orders, results and immunization messages, and terminate at an on-site interface engine. None is built or live.

C0321Does AuroraMed support FHIR?

FHIR R4 is planned, not built. The design describes a patient-access API, bulk export and subscriptions. Listing a standard is not a claim of conformance.

C0322Is SMART on FHIR supported?

SMART App Launch is a design target for the planned FHIR API and is not implemented.

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?

DICOM, PACS and RIS functions are designed, with an on-site image store. Nothing is built; imaging results in the pilot are synthetic entries.

C0325Can AuroraMed connect to laboratory analyzers?

Analyzer and middleware connections using common lab protocols are designed. Not built; the pilot publishes synthetic lab results.

C0326Does AuroraMed support e-prescribing?

E-prescribing, controlled-substance prescribing and prescription-monitoring checks are not built. They are the largest single package and need external certification time.

C0327Can claims go to a clearinghouse?

X12 claims, eligibility and remittance are designed and not built. No clearinghouse partner has been chosen.

C0328Are payer eligibility checks available?

Eligibility checks are planned with no partner and are not built.

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?

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?

Not yet. Drug knowledge bases are licensed content and interaction checking is not part of the pilot.

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.