You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During our mappings, we repeatedly encountered the ZIBs Bereik and TijdsInterval. It seems that these two ZIBs do not represent a clinical domain, but rather a "format type".
In openEHR, Bereik could refer to variable of type "Interval: Quantity" (Upper/Lower) in combination with "Quantity", while TijdsInterval could refer to variable of types "Interval: Duration (Upper/Lower)" and "Duration". We also found an alternative for TijdsInterval in Medicatieafspraak, where we could nicely map each variable of the ZIB (start date, end date and duration) using the archetype openEHR-EHR-CLUSTER.therapeutic_direction.v1.
Since the mapping of Bereik and TijdsInterval can be done in different archetypes, it seems that creating a specific template for these two ZIBs is therefore not strictly required. Although, it would be nice to get your thoughts on this.
The text was updated successfully, but these errors were encountered:
During our mappings, we repeatedly encountered the ZIBs Bereik and TijdsInterval. It seems that these two ZIBs do not represent a clinical domain, but rather a "format type".
In openEHR, Bereik could refer to variable of type "Interval: Quantity" (Upper/Lower) in combination with "Quantity", while TijdsInterval could refer to variable of types "Interval: Duration (Upper/Lower)" and "Duration". We also found an alternative for TijdsInterval in Medicatieafspraak, where we could nicely map each variable of the ZIB (start date, end date and duration) using the archetype openEHR-EHR-CLUSTER.therapeutic_direction.v1.
Since the mapping of Bereik and TijdsInterval can be done in different archetypes, it seems that creating a specific template for these two ZIBs is therefore not strictly required. Although, it would be nice to get your thoughts on this.
The text was updated successfully, but these errors were encountered: