Cumuluz Translate Implementation Guide
0.1.0 - ci-build
Cumuluz Translate Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
| Cumuluz R4 Translation And Validation CapabilityStatement |
CapabilityStatement for the R4-facing translation and validation surface exposed under /fhir/r4. |
| Cumuluz R4 to STU3 Translation CapabilityStatement |
CapabilityStatement for the explicit reverse translation surface exposed under /fhir/r4-stu3. |
| Cumuluz STU3 Translation CapabilityStatement |
CapabilityStatement for the same-version Dutch STU3 translation surface exposed under /fhir/stu3. |
| Cumuluz STU3 to R4 Translation CapabilityStatement |
CapabilityStatement for the cross-version translation surface exposed under /fhir/stu3-r4. |
These are custom operations that can be supported by and/or invoked by systems conforming to this implementation guide.
| QuestionnaireResponse Extraction |
System-level operation for extracting supported QuestionnaireResponses into an R4 resource Bundle selected by profile or questionnaire canonical. |
| R4 Resource Validate |
Operation for validating an R4 resource against its meta.profile or a requested R4 profile parameter. |
| Supported Dutch STU3 to R4 Transform |
System-level operation for translating a supported Dutch STU3 source resource or bundle into a supported R4 target profile. |
| Supported Dutch STU3 to STU3 Transform |
System-level operation for translating a supported Dutch STU3 source resource into a supported Dutch STU3 target profile. |
| Supported R4 to Dutch STU3 Transform |
System-level operation for translating a supported R4 source resource into a supported Dutch STU3 target profile. |
| Supported R4 to R4 Transform |
System-level operation for translating a supported R4 source resource into a supported R4 target profile. |
These define data models that represent the domain covered by this implementation guide in more business-friendly terms than the underlying FHIR resources.
| Logical Model: Allergy Intolerance |
Canonical intermediate logical model for AllergyIntolerance translation. It is shaped to the AllergyIntolerance core structure, aligned with eu-base as the structural baseline, and extended only where Dutch zib and nl-core allergy semantics require explicit fields. |
| Logical Model: Allergy Intolerance Note |
Named logical child type for AllergyIntolerance notes so author metadata can survive the intermediate logical model. |
| Logical Model: Allergy Intolerance Reaction |
Named logical child type for allergy reaction details in the intermediate allergy intolerance model. |
| Logical Model: Allergy Intolerance Reference |
Named logical child type for AllergyIntolerance references that may carry the Dutch practitionerrole-reference extension. |
| Logical Model: Alternate Dose |
A typed alternate medication dose and the circumstance in which it applies. |
| Logical Model: Anatomical Location |
Reusable structured anatomical location detail aligned with openEHR anatomical-location semantics and carried only when a target profile has an explicit home. |
| Logical Model: Appointment |
Canonical intermediate logical model for Appointment translation. It is shaped closely to R4 Appointment while preserving Dutch STU3 additions only where they have a target home. |
| Logical Model: Appointment Participant |
Named logical child type for appointment participants that may carry a Dutch practitionerrole-reference extension. |
| Logical Model: Care Team |
Canonical intermediate logical model for CareTeam translation. It is shaped closely to R4 CareTeam while preserving Dutch STU3 practitioner role handling explicitly where needed. |
| Logical Model: Care Team Participant |
Named logical child type for care team participants that may carry a Dutch practitionerrole-reference extension. |
| Logical Model: CarePlan |
Canonical intermediate logical model for CarePlan-shaped nl-core routes. |
| Logical Model: CarePlan Activity |
CarePlan activity detail semantics used by nl-core care plan routes. |
| Logical Model: Communication Payload |
Typed communication request payload content. |
| Logical Model: CommunicationRequest |
Canonical intermediate logical model for CommunicationRequest translation. It is source-family neutral and includes the R4 request semantics needed across STU3/BgZ sources. |
| Logical Model: Composition |
Canonical intermediate logical model for Composition-shaped nl-core routes. |
| Logical Model: Composition Attester |
An attestation of a composition. |
| Logical Model: Composition Event |
Clinical event represented by a composition. |
| Logical Model: Composition Relates To |
Relationship between this composition and another document. |
| Logical Model: Composition Section |
Composition section semantics used by nl-core report routes. |
| Logical Model: Consent |
Canonical intermediate logical model for Consent translation. It is source-family neutral and maps the R4 Consent shape that can be reached from STU3/BgZ sources through the converter. |
| Logical Model: Coverage |
Canonical intermediate logical model for Coverage-shaped nl-core routes. |
| Logical Model: Coverage Class |
Coverage class, plan, group, or subdivision. |
| Logical Model: Coverage Cost Exception |
An exception to a beneficiary cost-sharing rule. |
| Logical Model: Coverage Cost To Beneficiary |
Cost-sharing amount and exceptions applicable to a beneficiary. |
| Logical Model: Device |
Canonical intermediate logical model for Device translation. It is source-family neutral and mirrors the R4 Device resource shape for STU3/BgZ reuse. |
| Logical Model: Device Name |
A typed name assigned to a device. |
| Logical Model: Device Property |
Reusable R4 Device property content. |
| Logical Model: Device Specialization |
A device capability or specialization. |
| Logical Model: Device UDI Carrier |
Reusable R4 Device UDI carrier content. |
| Logical Model: Device Version |
A typed version of a device or component. |
| Logical Model: DeviceRequest |
Canonical intermediate logical model for medical-device-request translation. It follows R4 DeviceRequest rather than relabelling a device order as a service request. |
| Logical Model: DeviceRequest Parameter |
A device request parameter and its typed value. |
| Logical Model: DeviceUseStatement |
Logical intermediate model for DeviceUseStatement translation. It is source-family neutral and captures the R4 request/requester shape independent of the STU3 source. |
| Logical Model: Diagnostic Detail |
Typed coded, narrative, referenced, or attached diagnostic request or testing detail. |
| Logical Model: DiagnosticReport |
Canonical intermediate logical model for DiagnosticReport-shaped nl-core routes. |
| Logical Model: Directive Detail |
Typed directive detail represented by code, narrative, reference, or attachment. |
| Logical Model: DocumentReference |
Canonical intermediate logical model for DocumentReference-shaped nl-core routes. |
| Logical Model: Encounter |
Canonical intermediate logical model for Encounter translation. It is shaped to the R4 Encounter structure where practical, while keeping the Dutch STU3 zib encounter additions explicit. |
| Logical Model: Encounter Class History |
A prior encounter class and the period during which it applied. |
| Logical Model: Encounter Diagnosis |
Diagnosis details associated with an encounter. |
| Logical Model: Encounter Hospitalization |
Named logical child type for encounter hospitalization details that survive the logical handoff. |
| Logical Model: Encounter Location |
Location details associated with an encounter. |
| Logical Model: Encounter Participant |
Named logical child type for encounter participant details. |
| Logical Model: Encounter Reference |
Named logical child type for encounter references that may carry a Dutch practitionerrole-reference extension. |
| Logical Model: Encounter Status History |
A prior encounter status and the period during which it applied. |
| Logical Model: EpisodeOfCare |
Canonical intermediate logical model for EpisodeOfCare-shaped nl-core routes. |
| Logical Model: EpisodeOfCare Status History |
A prior episode status and its effective period. |
| Logical Model: Extraction Bundle |
Generic intermediate bundle graph populated by maps before materialization into a FHIR Bundle. |
| Logical Model: Extraction Entry |
Generic mapped instruction for one resource entry in an extraction Bundle. The map owns target routing metadata and the logical resource body. |
| Logical Model: Flag |
Canonical intermediate logical model for Flag-shaped nl-core routes. |
| Logical Model: Functional Or Mental Status |
Canonical intermediate logical model for FunctionalOrMentalStatus to Observation translation. It is shaped to the Observation core structure, aligned with eu-base medical test result semantics as the structural baseline, and extended with Dutch zib and nl-core functional or mental status semantics only where needed. |
| Logical Model: Functional Or Mental Status Component |
Named logical child type for Observation.component content in the intermediate functional or mental status model. |
| Logical Model: Functional Or Mental Status Reference Range |
Named logical child type for Observation.referenceRange content in the intermediate functional or mental status model. |
| Logical Model: Goal |
Canonical intermediate logical model for Goal translation. It is source-family neutral and aligns to the R4 Goal structure for translation reuse. |
| Logical Model: Goal Target |
Typed goal target with measure, detail, due date, outcome, and comment semantics. |
| Logical Model: Immunization |
Canonical intermediate logical model for Immunization-shaped nl-core routes. |
| Logical Model: Immunization Education |
Educational material presented in connection with an immunization. |
| Logical Model: Immunization Reaction |
Reaction observed following an immunization. |
| Logical Model: ImmunizationRecommendation |
Canonical intermediate logical model for ImmunizationRecommendation-shaped nl-core routes. |
| Logical Model: Location |
Canonical intermediate logical model for Location-shaped nl-core routes. |
| Logical Model: Location Hours Of Operation |
Recurring opening hours for a location. |
| Logical Model: Location Position |
Geographic coordinates for a location. |
| Logical Model: Media |
Canonical intermediate logical model for Media-shaped nl-core routes. |
| Logical Model: Medication |
Canonical intermediate logical model for Medication-shaped nl-core routes. |
| Logical Model: Medication Dispense |
Canonical intermediate logical model for administration agreement to medication dispense translation. It is shaped closely to R4 MedicationDispense with explicit Dutch source additions only where needed. |
| Logical Model: Medication Dosage |
Named logical child type for medication dosage details in the intermediate medication models. |
| Logical Model: Medication Ingredient |
A coded or referenced medication ingredient and its strength. |
| Logical Model: Medication Performer |
Named logical child type for medication dispense performers. |
| Logical Model: Medication Reference |
Named logical child type for medication-related references that may carry a Dutch practitionerrole-reference extension. |
| Logical Model: Medication Request |
Canonical intermediate logical model for medication agreement to medication request translation. It is shaped closely to R4 MedicationRequest with explicit Dutch source additions only where needed. |
| Logical Model: Medication Statement |
Canonical intermediate logical model for medication use to medication statement translation. It is shaped closely to R4 MedicationStatement with explicit Dutch source additions only where needed. |
| Logical Model: Medication Use Detail |
Reusable coded, narrative, referenced, or attached medication-use detail. |
| Logical Model: Metadata |
Canonical intermediate logical model for provenance and exchange metadata. It is shaped closely to R4 Provenance so audit and lineage semantics remain reversible across target families. |
| Logical Model: Metadata Agent |
Named logical child type for provenance agents in the intermediate metadata model. |
| Logical Model: Metadata Entity |
Named logical child type for entities participating in a provenance activity. |
| Logical Model: Nutrition Enteral Administration |
A scheduled enteral formula administration. |
| Logical Model: Nutrition Enteral Formula |
Enteral formula composition and administration instructions. |
| Logical Model: NutritionOrder |
Canonical intermediate logical model for NutritionOrder-shaped nl-core routes. |
| Logical Model: Observation |
Canonical intermediate logical model for Observation translation. It is source-family neutral and aligns with the R4 Observation resource for reuse across source variants. |
| Logical Model: Observation Component |
Reusable typed observation component or analyte result detail. |
| Logical Model: Observation Protocol |
Reusable observation protocol detail such as measurement location, cuff size, method, device, or formula. |
| Logical Model: Observation State |
Reusable observation state context such as patient position, exertion, or other measurement conditions. |
| Logical Model: Organization |
Canonical intermediate logical model for Organization-shaped nl-core routes. |
| Logical Model: Organization Contact |
Contact details for an organization-shaped nl-core route. |
| Logical Model: Patient |
Canonical intermediate logical model for Patient translation. It is shaped to the full Patient core structure, aligned with eu-base as the structural baseline, and extended with Dutch zib and nl-core patient semantics using future-oriented normalized field names. |
| Logical Model: Patient Communication |
Named logical child type for patient communication details in the intermediate patient model. |
| Logical Model: Patient Communication Proficiency |
Named logical child type for patient language proficiency details in the intermediate patient model. |
| Logical Model: Patient Contact |
Named logical child type for patient contact details in the intermediate patient model. |
| Logical Model: Patient Link |
Named logical child type for patient linkage details in the intermediate patient model. |
| Logical Model: Patient Nationality |
Named logical child type for patient nationality details in the intermediate patient model. |
| Logical Model: Practitioner |
Canonical intermediate logical model for Practitioner translation. It is source-family neutral and mirrors the R4 Practitioner profile surface for STU3/BgZ-neutral reuse. |
| Logical Model: PractitionerRole |
Canonical intermediate logical model for PractitionerRole translation. It is source-family neutral and mirrors the R4 PractitionerRole structure for STU3/BgZ-neutral conversion workflows. |
| Logical Model: PractitionerRole Available Time |
Recurring availability for a practitioner role. |
| Logical Model: PractitionerRole Not Available |
A described period when a practitioner role is unavailable. |
| Logical Model: Problem |
Canonical intermediate logical model for Problem to Condition translation. It is shaped to the full Condition core structure, aligned with eu-base as the structural baseline, and extended with Dutch zib and nl-core problem semantics using future-oriented normalized field names. |
| Logical Model: Problem Body Site |
Problem body site details kept together so anatomical location, laterality, and future body structure references survive the intermediate logical model without losing their relationship. |
| Logical Model: Problem Evidence |
Named logical child type for condition evidence details in the intermediate problem model. |
| Logical Model: Problem Specific Detail |
Typed problem-specific detail preserved from XIB as text or a reference. |
| Logical Model: Problem Stage |
Named logical child type for condition stage details in the intermediate problem model. |
| Logical Model: Procedure |
Canonical intermediate logical model for Procedure translation. It is shaped to the full Procedure core structure, aligned with eu-base as the structural baseline, and extended with Dutch zib and nl-core procedure semantics using future-oriented normalized field names. |
| Logical Model: Procedure Body Site |
Procedure body site details kept together so anatomical location and laterality survive the intermediate logical model without losing their relationship. |
| Logical Model: Procedure Focal Device |
Named logical child type for procedure focal device details in the intermediate procedure model. |
| Logical Model: Procedure Performer |
Named logical child type for procedure performer details in the intermediate procedure model. |
| Logical Model: Questionnaire Answer |
Normalized single questionnaire answer slot populated from a version-specific QuestionnaireResponse item. |
| Logical Model: Questionnaire Form |
Shared intermediate logical model for QuestionnaireResponse extraction. Version-specific StructureMaps normalize questionnaire items into named generic answers and groups before extraction maps interpret those names into clinical logical resources. |
| Logical Model: Questionnaire Telecom |
Normalized grouped questionnaire telecom answer populated from a repeated phone or email item group. |
| Logical Model: RelatedPerson |
Canonical intermediate logical model for RelatedPerson translation. It is source-family neutral and mirrors the R4 RelatedPerson shape for STU3/BgZ-neutral reuse. |
| Logical Model: RelatedPerson Communication |
Language and preference details for communication with a related person. |
| Logical Model: Service Request Detail |
Typed coded, narrative, referenced, or attached service-request detail. |
| Logical Model: ServiceRequest |
Canonical intermediate logical model for ServiceRequest-shaped nl-core routes. |
| Logical Model: Specimen |
Canonical intermediate logical model for Specimen-shaped nl-core routes. |
| Logical Model: Specimen Container |
Typed specimen container aligned with R4 Specimen.container. |
| Logical Model: Specimen Physical Property |
Typed physical property of a specimen. |
| Logical Model: Specimen Processing |
Typed specimen processing step aligned with R4 Specimen.processing. |
| Logical Model: Specimen Storage |
Typed specimen storage condition. |
| Logical Model: Specimen Transport |
Typed specimen transport condition. |
These define constraints on FHIR resources for systems conforming to this implementation guide.
| BgZ Patient Stub |
Lightweight local profile stub that anchors the BgZ Patient canonical used in the published examples. |
| Translation Governance Report |
FHIR Parameters profile for a translation governance report carried in transform responses. The report groups translated leaf values as mapped, changed, added, or deleted. |
| XIB Advance Directive |
XIB consent profile based on plain R4 Consent for supported advance-directive data points. Source-specific semantics are represented by explicit mapped values and extension slices instead of source profile inheritance. |
| XIB AllergyIntolerance |
XIB allergy intolerance target profile based on EU Base AllergyIntolerance with implemented nl-core data points. |
| XIB Appointment |
XIB appointment target profile for implemented appointment data points. |
| XIB CarePlan |
Generic XIB care plan target for nl-core CarePlan profiles with explicit lifecycle milestone extension homes. |
| XIB CareTeam |
XIB care team target profile based on plain R4 CareTeam because no suitable EU Base CareTeam profile is installed. |
| XIB Composition |
Generic XIB composition target for nl-core Composition profiles. |
| XIB Contact Person |
XIB related person profile based on plain R4 RelatedPerson for supported contact-person data points. |
| XIB Coverage |
Generic XIB coverage target for nl-core Coverage profiles. |
| XIB DeviceRequest |
XIB medical device request target extending native R4 DeviceRequest. |
| XIB DiagnosticReport |
Generic XIB diagnostic report target for nl-core DiagnosticReport profiles with explicit lab-result detail extension homes. |
| XIB DocumentReference |
Generic XIB document reference target for nl-core DocumentReference profiles. |
| XIB Encounter |
XIB encounter target profile based on plain R4 Encounter because no suitable EU Base Encounter profile is installed. Supported Dutch encounter data points are mapped directly through the logical model. |
| XIB EpisodeOfCare |
Generic XIB episode of care target for nl-core EpisodeOfCare profiles. |
| XIB Flag |
Generic XIB flag target for nl-core Flag-based profiles. |
| XIB Functional or Mental Status Observation |
XIB observation profile for functional or mental status, based on EU Base medical test result and populated through the logical model. |
| XIB Generic Condition |
Generic XIB condition target for nl-core Condition-based source profiles that are not the specific XIB Problem/Diagnosis profile. It preserves the reviewed Condition-shaped logical surface without claiming problem-specific constraints. |
| XIB Generic Observation |
Generic XIB observation target for nl-core Observation-based source profiles that do not have a more specific XIB observation profile. It carries only reviewed generic observation semantics and explicit extension homes for measurement context. |
| XIB Immunization |
Generic XIB immunization target for nl-core Immunization profiles. |
| XIB ImmunizationRecommendation |
Generic XIB immunization recommendation target for nl-core ImmunizationRecommendation profiles. |
| XIB Inform Relatives Request |
XIB communication request profile for inform-relatives request data points. |
| XIB Location |
Generic XIB location target for nl-core Location profiles. |
| XIB Media |
Generic XIB media target for nl-core Media profiles. |
| XIB Medical Device |
XIB device use statement profile based on plain R4 DeviceUseStatement for medical device use data points. |
| XIB Medical Device Product |
XIB device profile based on plain R4 Device for medical device product data points with explicit extension homes for reviewed device details. |
| XIB Medical Policy Goal |
XIB goal profile for medical policy goal data points. |
| XIB Medication |
Generic XIB medication target for nl-core Medication profiles. |
| XIB Medication Administration Agreement / Dispense |
XIB medication dispense target profile for implemented dispense and Dutch administration-agreement data points. |
| XIB MedicationRequest |
XIB medication request target profile based on EU Base MedicationRequest with explicit extension homes for reviewed medication-order details. |
| XIB MedicationStatement |
XIB medication statement target profile based on EU Base MedicationStatement. |
| XIB NutritionOrder |
Generic XIB nutrition order target for nl-core NutritionOrder profiles. |
| XIB Organ Donation Choice Registration |
XIB observation profile for organ donation choice registration data points. |
| XIB Organization |
Generic XIB organization target for nl-core Organization profiles. |
| XIB Patient |
XIB patient target profile based on EU Base Patient. Supported Dutch patient data points are carried as explicit XIB extension slices instead of by inheriting from source-specific profiles. |
| XIB Position Regarding Euthanasia |
XIB observation profile for position regarding euthanasia data points. |
| XIB Practitioner |
XIB practitioner profile based on EU Base Practitioner for supported health-professional practitioner data points. |
| XIB PractitionerRole |
XIB practitioner role profile based on EU Base PractitionerRole for supported health-professional practitioner-role data points. |
| XIB Preferred Place Of Death |
XIB observation profile for preferred place of death data points. |
| XIB Problem/Diagnosis |
XIB problem/diagnosis target profile based on EU Base Condition with implemented nl-core Problem data points and explicit extension homes for reviewed problem/diagnosis details. |
| XIB Procedure |
XIB procedure target profile based on plain R4 Procedure. EU Base Procedure is not used as the parent because it requires performed[x], which is not guaranteed by every supported source route; supported nl-core procedure data points are carried as explicit XIB extension slices. |
| XIB Provenance |
XIB provenance target profile for implemented metadata data points. |
| XIB Sense Of Purpose |
XIB observation profile for sense of purpose data points. |
| XIB ServiceRequest |
Generic XIB service request target for nl-core ServiceRequest profiles. |
| XIB Specific Care Wishes |
XIB observation profile for specific care wishes data points. |
| XIB Specimen |
Generic XIB specimen target for nl-core Specimen profiles with explicit specimen-handling extension homes. |
| XIB Treatment Directive |
XIB consent profile based on plain R4 Consent for supported treatment-directive data points. Source-specific semantics are represented by explicit mapped values and extension slices instead of source profile inheritance. |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| Dutch PractitionerRole Reference |
XIB-packaged compatibility definition for the Dutch practitioner-role reference extension used on actor references. |
| Translation target profile |
Selects the target profile for one Bundle entry in a transform request. |
| Validation issue count: error |
Counts the number of validation issues with severity error or fatal. |
| Validation issue count: information |
Counts the number of validation issues with severity information. |
| Validation issue count: warning |
Counts the number of validation issues with severity warning. |
| Validation relaxed issue count |
Counts validation issues relaxed by the runtime. |
| XIB Administration Agreement Reason |
XIB-local definition for the Dutch administration agreement reason extension used by supported medication dispense mappings. |
| XIB Advance Directive Details |
XIB extension for advance-directive details that have no direct R4 Consent element. |
| XIB Alternate Dose |
A conditional alternate medication dose. |
| XIB CarePlan Details |
XIB extension for planning-specific care plan identity, name, and expiry semantics. |
| XIB CarePlan Lifecycle Milestones |
XIB extension for care-plan lifecycle milestones represented by openEHR action states. |
| XIB Comment |
Reusable XIB-owned replacement for Dutch free-text comment extensions. |
| XIB Consent Additional Source |
XIB extension preserving an additional directive source as the original attachment, identifier, or reference choice. |
| XIB Device Details |
XIB extension for medical device details beyond the base Device fields used by the current XIB profile. |
| XIB DeviceRequest Requester On Behalf Of |
XIB-local extension for the organization on behalf of which a device request requester acted. |
| XIB Diagnostic Report Details |
XIB extension for diagnostic report request, diagnosis, and testing details. |
| XIB Diagnostic Test Request Detail |
Typed coded, narrative, referenced, or attached diagnostic test-request detail. |
| XIB Diagnostic Testing Detail |
Typed coded, narrative, referenced, or attached testing detail. |
| XIB Directive Detail |
Typed coded, narrative, referenced, or attached detail belonging to a care directive. |
| XIB Directive Verification Details |
XIB extension for coded directive-verification semantics from Dutch STU3 that cannot use the R4 Consent.verification.verifiedWith Reference element. |
| XIB Goal Details |
XIB extension for medical policy goal details beyond the R4 Goal base. |
| XIB Goal Target |
Typed XIB goal target. |
| XIB Lab Result Details |
XIB extension for laboratory report and analyte details that have no direct base DiagnosticReport element. |
| XIB Legally Capable Of Medical Treatment Decisions |
XIB-owned replacement for the PZP legal-capability extension. |
| XIB Life Stance |
XIB-local definition for the existing Dutch life stance extension used by supported patient mappings. |
| XIB Medical Device Details |
XIB extension preserving Dutch medical-device responsibility and clinical-reason references. |
| XIB Medication Additional Information |
XIB-local definition for the Dutch medication additional information extension used by supported medication mappings. |
| XIB Medication Dosage Details |
XIB extension for Dutch dosage semantics that have no native R4 Dosage element. |
| XIB Medication Order Details |
XIB extension for medication-order details that exceed R4 MedicationRequest and EU Base MedicationRequest. |
| XIB Medication Performer On Behalf Of |
Organization on whose behalf a medication dispense performer acted. |
| XIB Medication Period Of Use |
XIB-local definition for the Dutch medication period-of-use extension used by supported medication mappings. |
| XIB Medication Statement Details |
XIB extension for medication-use details beyond R4 MedicationStatement. |
| XIB Medication Stop Type |
XIB-local definition for the Dutch medication stop type modifier extension used by supported medication mappings. |
| XIB Medication Treatment |
XIB-local definition for the Dutch medication treatment identifier extension used by supported medication mappings. |
| XIB Medication Use As Agreed Indicator |
XIB-local definition for the Dutch medication-use as-agreed indicator extension used by supported medication mappings. |
| XIB Medication Use Detail |
Typed coded, narrative, referenced, or attached medication-use detail. |
| XIB Medication Use Duration |
XIB-local definition for the Dutch medication use duration extension used by supported medication mappings. |
| XIB Medication Use Prescriber |
XIB-local definition for the Dutch medication-use prescriber extension used by supported medication mappings. |
| XIB MedicationRequest Requester On Behalf Of |
XIB-local extension for the organization on behalf of which a medication request requester acted. |
| XIB MedicationStatement Taken |
XIB-local extension for the STU3/R3 medication-use taken code when translating to R4 MedicationStatement. |
| XIB Observation Measurement Context |
XIB extension for observation state and protocol details such as cuff size, position, exertion, and measurement context. |
| XIB Patient Legal Status |
XIB-local definition for the existing Dutch patient legal status extension used by supported patient mappings. |
| XIB Preferred Pharmacy |
XIB-local definition for the existing Dutch preferred pharmacy extension used by supported patient mappings. |
| XIB Problem Details |
XIB extension for problem/diagnosis details that have no stable R4 or EU Base element. |
| XIB Procedure Details |
XIB extension for procedure planning, ordering, narrative, and execution details without a stable R4 Procedure element. |
| XIB Request Status Detail |
Coded source request status retained alongside the R4 status code. |
| XIB Service Request Detail |
Typed coded, narrative, referenced, or attached request detail. |
| XIB Service Request Details |
XIB extension for request semantics beyond R4 ServiceRequest. |
| XIB Specimen Container |
Typed specimen container. |
| XIB Specimen Details |
XIB extension for complete specimen collection, handling, and identification semantics. |
| XIB Specimen Handling |
XIB extension for specimen handling, quality, hazard, and adequacy details. |
| XIB Specimen Physical Property |
Typed physical specimen property. |
| XIB Specimen Processing |
Typed specimen processing step. |
| XIB Specimen Storage |
Typed specimen storage condition. |
| XIB Specimen Transport |
Typed specimen transport condition. |
| XIB Stoma Reference |
XIB extension preserving the stoma associated with a bowel-function observation. |
| XIB Structured Anatomical Location |
XIB extension for anatomical-location details that exceed the base CodeableConcept bodySite shape. |
| XIB Vaccination Recommendation Order Status |
XIB extension preserving the Dutch vaccination recommendation order status. |
These define identifier and/or code system identities used by systems conforming to this implementation guide.
| Dutch BSN NamingSystem |
Minimal NamingSystem definition so examples that use the BSN identifier system can resolve offline. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| bundle-transform-request |
Example Bundle transform request with entry-level target profile overrides. |
| patient-transform-request |
Example BgZ transform request for a single Patient. |
| patient-transform-response |
Example transform response for a single Patient. |
| patient-validate-request |
Example R4 validation request for a translated Patient. |
| patient-validate-response |
Example validation result for a translated Patient. |
| patient-validate-response-fail |
Example validation failure result for a translated Patient. |