Atrius India Core FHIR Implementation Guide
0.1.0 - ci-build
Atrius India Core FHIR Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
HIS exposes inbound FHIR Messaging for consequence workflows (LIS/PACS results, future ABDM/NHCX). This is complementary to Subscriptions (best-effort resource-change notifications).
POST {HIS}/api/v1/$process-message (alias /process-message)
Request body: Bundle with type = message, entry[0] = MessageHeader.
CodeSystem: AtriusMessageEvents at https://atrius.in/fhir/message-events. The composed event URIs ({system}/{code}) are also registered on atrius-in-message-events-ns so MessageDefinition.eventUri has a definition.
| Code | Event URI | MessageDefinition | Focus |
|---|---|---|---|
ack |
…/message-events/ack |
(response only) | — |
ping |
…/message-events/ping |
— | smoke / connectivity |
lab-result |
…/message-events/lab-result |
atrius-md-lab-result |
DiagnosticReport (+ Observation) |
imaging-result |
…/message-events/imaging-result |
atrius-md-imaging-result |
DiagnosticReport (+ ImagingStudy) |
Set MessageHeader.eventUri (preferred) or eventCoding with system = https://atrius.in/fhir/message-events and the code above.
HIS applies R4 reliable-messaging semantics:
Bundle.id, else MessageHeader.id.message_dedup on HIS_DATABASE_URL) or in-memory when unset.Successful processing returns a message Bundle whose MessageHeader.eventUri is https://atrius.in/fhir/message-events/ack, with response.identifier pointing at the request MessageHeader id and response.code = ok (or transient-error / fatal-error on failure).
New inbound message events MUST be added to AtriusMessageEvents and, for consequence workflows, a MessageDefinition under input/fsh/messaging/. Heuristic string matching in the HIS dispatcher is a migration bridge — the CodeSystem/MessageDefinition pair is the contract.