MedNet interface implementation guide
0.15.0 - CI Build
MedNet interface implementation guide
0.15.0 - CI Build
MedNet interface implementation guide - Local Development build (v0.15.0). See the Directory of published versions
Contents:
In order to show only the relevant informations on this IG, we created in some cases our own profiles based on, or copy of fhir.ch profiles. If your System already support some of those profiles, you should be able to reuse them
We will list on this page the different profiles that differs from standard profiles and the reason why we provide our own implementation for those profiles
This bundle is based on the IPS recommendations, with some adaptations:
Composition.section.text has cardinality 0..1 instead of 1..1
This field is not necessary in the context of use with mednet
section:insuranceData has been added
section:annotations has been added
section:documents has been added
contact
Contact relationship extended support including FamilyMember or others like Employer, Emergency contact etc...
identifier has cardinality 0..* instead of 1..*
The identifier is not mandatory in the mednet context
dosage:nonstructured has cardinality 0..1 instead of 1..1
Non structured dosage is not mandatory in the mednet context
form is not supported by mednet whereas it has cardinality 1..1 on chmed20af-card-medication profile
The medication form is not useful in the mednet context
dataAbsentReason is not supported by MedNet, whereas base profile (vital-sign) attribute MustSupport is set to true
This information is not used in the mednet context
component is not supported by MedNet, whereas base profile (vital-sign) attribute MustSupport is set to true
In general this element has no function in a body weight context
dataAbsentReason is not supported by MedNet, whereas base profile (vital-sign) attribute MustSupport is set to true
This information is not used in the mednet context
component is not supported by MedNet, whereas base profile (vital-sign) attribute MustSupport is set to true
In general this element has no function in a body height context
dataAbsentReason is not supported by MedNet, whereas base profile (vital-sign) attribute MustSupport is set to true
This information is not used in the mednet context
component is not supported by MedNet, whereas base profile (vital-sign) attribute MustSupport is set to true
In general this element has no function in a body mass index context
dataAbsentReason is not supported by MedNet, whereas base profile (vital-sign) attribute MustSupport is set to true
This information is not used in the mednet context
component.dataAbsentReason is not supported by MedNet, whereas base profile (vital-sign) attribute MustSupport is set to true
This information is not used in the mednet context
There is actually no official profile for the blood group. That's why we defined our own profile
dataAbsentReason is not supported by MedNet, whereas base profile (vital-sign) attribute MustSupport is set to true
This information is not used in the mednet context
component.dataAbsentReason is not supported by MedNet, whereas base profile (vital-sign) attribute MustSupport is set to true
This information is not used in the mednet context