Skip to content

decisions.md

Latest commit

 

History

History
21 lines (18 loc) · 3.02 KB

decisions.md

File metadata and controls

21 lines (18 loc) · 3.02 KB
Raw

Profiling authoring decisions taken:

10/07/2025

  • RelatedPerson.relationship[relationship] contains distinct codes for curator/mentor and brother/sister while the form allows only the option to select them both. From the form is not possible then to map this to FHIR as you would not know which code to use. We will use the zib codes and don't give to much credit to the form here.
  • PractitionerRole - "430" "ZorgverlenerRol" is not yet implemented in the Nictiz FHIR profiles, because this is mapped in the resources that refer to the PractitionerRole. It is not mapped in PractitionerRole.code. MM: zorgverlenersrol gaat eruit, is nu ook doorgevoerd in Art-Decor. Mapping dus niet nodig
  • ACPMedicalPolicyGoal - Mapping on Goal in stead of Observation.

22/07/2025

  • ExtLegallyCapableMedicalTreatmentDecisions naming is set and extension is considerd Ok. 2/2/2026: Changed to ExtPatientLegallyCapableMedicalTreatmentDecisions
  • Patient invariant about mandating a legal contact person when LegallyCapableMedicalTreatmentDecisions is false will become a warning
  • All ContactPersons will be populated in the RelatedPerson resource, optionally in the Patient.contact field. The http://hl7.org/fhir/StructureDefinition/patient-relatedPerson extension should be used to link the contact persons.
  • Patient contactgegevens is in de zib 0..1 en dataset 0..1 maar in nl core 0..* - discussed with Lonekke and ok. Leave as it profiled in nl-core.
  • ACPPreferredPlaceOfDeath binding is set to extensible both in ArtDecor and FHIR.
  • On the question how to distingues the Encounter that took place for ACP: we will use both Encounter and Procedure with Procedure.code = SNOMED CT 713603004 - Advance care planning (procedure)

29/07/2025

  • The SNOMED code 713603004 for Medical Policy Goal in Goal.category is not a good fit, as it is too restrictive. Goals created outside the ACP context are also in scope. Therefore, we will not use a category code for now. Searching and retrieving Goals will be based on the input parameter for the bound ValueSet.
  • PreferredPlaceOfDeath is mapped to Observation. Although FHIR R5 suggests using Goal in CarePlan for advance directive agreements, we have decided to continue using Observation for this version.
  • The Observation.dataAbsentReason element is a suitable way to communicate unknown or not-asked information. We will add mappings to these elements as well.
  • For "Afspraak uitzetten ICD (BehandelAanwijzing)", we will reuse nl-core-TreatmentDirective2 and provide additional specifications on how "Afspraak uitzetten ICD (BehandelBesluit)" maps to Consent.provision.type and Consent.modifierExtension[specificationOther].valueString. Implementers will be directed to this profiling in the call for feedback section on the main page.
  • References to externally hosted ValueSets, such as GeslachtCodelijst, are not provided correctly by the IG publisher. See: https://nictiz.atlassian.net/browse/ZIBFHIR-356. If this issue persists upon publishing, we can mitigate it by removing ValueSet.meta.source from the zib package.