This scenario models a smooth handoff of a patient wellness summary from one facility to another using FHIR messaging patterns. The sending system packages the content in a bundle, addresses it with a message header, and follows a message definition that keeps processing predictable for receivers. The clinical tone remains routine: the transfer completes successfully and supports continuity of preventive care.
from zato_fhir.test.r4.v1 import Scenarios, TestData
for transfer in Scenarios.messaging:
patient = transfer.patient
for name in patient.name:
print(name.text)
definition = transfer.message_definition
print(definition.eventCoding)
header = transfer.message_header
ec = header.eventCoding
if ec is not None:
print(ec.code)
bundle = transfer.bundle
print(bundle.type_)
subscription = transfer.subscription
print(subscription.status)This scenario models a smooth handoff of a patient wellness summary from one facility to another using FHIR messaging patterns. The sending system packages the content in a bundle, addresses it with a message header, and follows a message definition that keeps processing predictable for receivers. The clinical tone remains routine: the transfer completes successfully and supports continuity of preventive care.
A subscription resource represents monitoring for similar transfers in the future, which is useful for testing notification pipelines and deduplication logic. Together, the resources exercise parsing of envelopes, resolution of definitions, and fan-out rules without introducing error narratives or failed deliveries in the synthetic dataset.
5 resources per instance, 50 total across 10 instances.
| FHIR resource type | Role in this scenario |
|---|---|
Patient | Person whose wellness record is transferred |
MessageDefinition | Rules and structure for the transfer message |
MessageHeader | Routing and event metadata for the message |
Bundle | Payload carrying the transferred wellness content |
Subscription | Channel that monitors for future transfer events |
FHIR resources per instance | 5 |
Total resources (10 instances) | 50 |
Distinct resource types | 5 |
Scenario identifier | `Scenarios.messaging` |
Get started with Zato and connect your systems in minutes.