EMR report delivery
What each entry in an EMR report activity's timeline means, and how a delivery attempt, its outcome and a retry are each recorded.
A Push to EMR action generates a report and hands it to the integration engine, which passes it to the
hospital's electronic medical record (EMR) system. Every stage is recorded on the activity, so the
timeline in Awell Care and the sub_activities array in the API show the same entries.
The handover and the outcome are separate entries
Awell hands the report to the integration engine and receives an acknowledgment that carries no outcome. The EMR's verdict arrives afterward, on a separate callback from the integration engine.
A send entry therefore means the report left Awell, not that the EMR accepted it.
What each entry means
action | Shown in Awell Care as | What it means |
|---|---|---|
send | "A request was sent to the integration provider." | Awell handed the report to the integration engine. Written once per delivery attempt. |
processed | "Integration request was processed successfully." | The EMR accepted the report. |
failed | "Integration request has failed." | The EMR rejected the report. |
failed_to_send | "A request was not able to be sent to the integration provider." | The attempt never reached the integration engine. The entry's error field carries the message. |
processed and failed each complete the activity, one as a success and the other as a failure.
Every entry carries the integration request ID in its object, which is the identifier to quote when
asking about a specific report.
A retry writes its own pair of entries
An attempt that can't reach the integration engine is retried. A delivery gets up to nine attempts in
total, with a growing delay that spreads them over roughly two hours. Each attempt writes its own
send first, then failed_to_send if it fails.
So an outage of the integration engine shows as repeated send and failed_to_send pairs on one
activity rather than a single failure line. The activity is completed as a failure only after the last
attempt is exhausted.
The same entries come back from the API
sub_activities is a field on the Activity type in the Orchestration API, and it is included in the
activity webhook payloads. See Webhook payloads for the
payload shape and Query activities for the queries that
return an activity.
Next steps
Next: EMR integration terminology defines the integration engine and the HL7 message types a hospital exchanges.
Patient Demographics Query (PDQ)
The PDQ integration reference: how Awell searches a Patient Demographics Supplier by identifier, what the request and response look like, and how Awell Care reacts.
The API call action
Call any REST or GraphQL API from inside a care flow to fetch or send data, and store the response in data points the flow can build logic on.