This scenario illustrates how a routine clinical read of a patient wellness record leaves a transparent, non-alarming audit footprint. A practitioner opens the chart for authorized care coordination, and the system records who accessed what, when, and in which context. The storyline assumes appropriate use: access is legitimate, successful, and free of security exceptions in the generated data.
from zato_fhir.test.r4.v1 import Scenarios, TestData
for access in Scenarios.audit_trail:
patient = access.patient
for name in patient.name:
print(name.text)
event = access.audit_event
if event.type_ is not None:
print(event.type_.code)
for sub in event.subtype:
print(sub.code)
prov = access.provenance
print(prov.recorded)
link = access.linkage
print(link.active)
basic = access.basic
for coding in basic.code.coding:
print(coding.code)
binary = access.binary
print(binary.contentType)
params = access.parameters
for param in params.parameter:
print(param.name)
outcome = access.operation_outcome
for issue in outcome.issue:
print(issue.severity)This scenario illustrates how a routine clinical read of a patient wellness record leaves a transparent, non-alarming audit footprint. A practitioner opens the chart for authorized care coordination, and the system records who accessed what, when, and in which context. The storyline assumes appropriate use: access is legitimate, successful, and free of security exceptions in the generated data.
Supporting resources connect the patient to the audited activity and bundle auxiliary payloads where needed. Provenance documents the origin of key assertions, linkage ties related records for traceability, and basic or binary artifacts can stand in for opaque extensions or attachments in integration tests. Parameters and operation outcome wrap the interaction so clients can assert that the operation completed successfully.
8 resources per instance, 80 total across 10 instances.
| FHIR resource type | Role in this scenario |
|---|---|
Patient | Subject of the accessed wellness record |
AuditEvent | Security or access log for the chart read |
Provenance | Assertion of who created or signed relevant data |
Linkage | Associations between related records for traceability |
Basic | Simple tag-like resource carrying scenario-specific metadata |
Binary | Opaque content such as a small attachment or payload |
Parameters | Input or output parameters for the audited operation |
OperationOutcome | Overall success indicator for the completed operation |
FHIR resources per instance | 8 |
Total resources (10 instances) | 80 |
Distinct resource types | 8 |
Scenario identifier | `Scenarios.audit_trail` |
Get started with Zato and connect your systems in minutes.