Belgian Pregnancy Status Implementation Guide
1.0.0 - STU
BE
This page is part of the eHealth FHIR Pregnancy Status Profiles for Belgium (v1.0.0: Release) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
These define data models that represent the domain covered by this implementation guide in more business-friendly terms than the underlying FHIR resources.
| Pregnancy Status Model |
Logical model for the pregnancy-status data. This is the minimal data set for the pregnancy status (consumed, for example, via Vitalink FHIR / MAGDA / VUTG / mijnburgerprofiel.be / mijngezondheid.be / caregivers). |
These define constraints on FHIR resources for systems conforming to this implementation guide.
| Pregnancy Status (administrative) |
Administrative pregnancy status: a single The detail observations — estimated date of delivery (LOINC There is no StructureDefinition per detail type; the slicing and profiling live
on the contained resources. Pregnancy status is for administrative sharing, not
clinical care; for clinical care the pregnancy is more commonly represented as a
|
These define sets of codes used by systems conforming to this implementation guide.
| Pregnancy status value set (BE) |
Codes describing the current pregnancy status of a woman, aligned with the IPS pregnancy status value set. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| Example gynaecologist |
Practitioner who records the pregnancy data in all examples. |
| Example pregnant woman |
Patient used by all pregnancy-status examples. |
| Pregnancy Status Contained Example |
Example of a pregnancy status observation using contained resources. |