This scenario packages the artifacts a wellness-oriented FHIR server typically publishes so clients know how to query, validate, and interoperate safely. A capability statement summarizes supported resources and interactions, while operation and search parameter definitions make behavior explicit for developers and test harnesses. Structure definitions and maps describe how local profiles relate to the base specification, supporting consistent validation pipelines.
from zato_fhir.test.r4.v1 import Scenarios, TestData
for publish in Scenarios.conformance:
cap = publish.capability_statement
print(cap.status)
op = publish.operation_definition
print(op.status)
sp = publish.search_parameter
print(sp.status)
comp = publish.compartment_definition
print(comp.status)
struct = publish.structure_definition
print(struct.status)
smap = publish.structure_map
print(smap.status)
ig = publish.implementation_guide
print(ig.status)
graph = publish.graph_definition
print(graph.status)
example = publish.example_scenario
print(example.status)This scenario packages the artifacts a wellness-oriented FHIR server typically publishes so clients know how to query, validate, and interoperate safely. A capability statement summarizes supported resources and interactions, while operation and search parameter definitions make behavior explicit for developers and test harnesses. Structure definitions and maps describe how local profiles relate to the base specification, supporting consistent validation pipelines.
An implementation guide ties the narrative together for human readers, and graph definitions help tools understand useful traversal patterns. An example scenario illustrates a happy-path exchange so onboarding teams can align documentation with executable tests. There is no patient in this bundle; it is purely conformance and knowledge metadata with a positive, production-ready posture in the synthetic data.
9 resources per instance, 90 total across 10 instances.
| FHIR resource type | Role in this scenario |
|---|---|
CapabilityStatement | Machine-readable summary of server features and supported resources |
OperationDefinition | Custom or extended operations the server implements |
SearchParameter | Searchable paths and modifiers exposed to clients |
CompartmentDefinition | Rules for compartment-based access scoping |
StructureDefinition | Profiles and constraints on wellness-related resources |
StructureMap | Declarative mapping between logical models or versions |
ImplementationGuide | Packaged documentation and artifact index for the server |
GraphDefinition | Recommended linked-data shapes for common queries |
ExampleScenario | Worked example of a successful interaction sequence |
FHIR resources per instance | 9 |
Total resources (10 instances) | 90 |
Distinct resource types | 9 |
Scenario identifier | `Scenarios.conformance` |
Get started with Zato and connect your systems in minutes.