This scenario supports organizations that need sharable definitions for wellness visit categories before any specific patient appears in the stream. A local code system captures friendly, policy-aligned labels used in scheduling and reporting, and a value set publishes the curated subset that applications should query at runtime. The narrative stays administrative: terminology is complete, consistent, and ready for downstream binding in profiles and forms.
from zato_fhir.test.r4.v1 import Scenarios, TestData
for setup in Scenarios.terminology_setup:
code_system = setup.code_system
print(code_system.status)
value_set = setup.value_set
print(value_set.status)
concept_map = setup.concept_map
print(concept_map.status)
naming = setup.naming_system
print(naming.status)
capabilities = setup.terminology_capabilities
print(capabilities.status)This scenario supports organizations that need sharable definitions for wellness visit categories before any specific patient appears in the stream. A local code system captures friendly, policy-aligned labels used in scheduling and reporting, and a value set publishes the curated subset that applications should query at runtime. The narrative stays administrative: terminology is complete, consistent, and ready for downstream binding in profiles and forms.
A concept map expresses how local codes align with SNOMED CT, which helps interoperability and analytics without implying clinical incidents. Naming system metadata anchors identifiers, and terminology capabilities describe what a server offers searchers and validators. There is no patient resource in this scenario; it is purely about vocabulary infrastructure.
5 resources per instance, 50 total across 10 instances.
| FHIR resource type | Role in this scenario |
|---|---|
CodeSystem | Local codes for wellness visit categories |
ValueSet | Published set of categories for application binding |
ConceptMap | Translation from local codes to SNOMED CT |
NamingSystem | Identifier namespace for the terminology artifacts |
TerminologyCapabilities | Declaration of terminology services and features supported |
FHIR resources per instance | 5 |
Total resources (10 instances) | 50 |
Distinct resource types | 5 |
Scenario identifier | `Scenarios.terminology_setup` |
Get started with Zato and connect your systems in minutes.