ConceptMap-ProbleemStatusCodelijst-to-Condition-Clinical-Status-Codes

Sourcenictiz.fhir.nl.stu3.zib2017#2.2.15:Nictiz FHIR NL STU3 Zib2017 (v3.0.2)
resourceTypeConceptMap
idProbleemStatusCodelijst-to-Condition-Clinical-Status-Codes
canonicalhttp://nictiz.nl/fhir/ConceptMap/ProbleemStatusCodelijst-to-Condition-Clinical-Status-Codes
version2.1.3
statusactive
publisherNictiz
nameProbleemStatusCodelijst-to-Condition-Clinical-Status-Codes
titleHCIM ProbleemStatusCodelijst to Condition Clinical Status Codes
descriptionMaps the HCIM ConcernForTransfer release 2017 terminology for ProblemStatus to the FHIR STU3 terminology associated with `Condition.clinicalStatus`.
copyrightCC0
sourceScopehttp://decor.nictiz.nl/fhir/ValueSet/2.16.840.1.113883.2.4.3.11.60.40.2.5.1.2--20171231000000
targetScopehttp://hl7.org/fhir/ValueSet/condition-clinical
sourceshttp://hl7.org/fhir/condition-clinical|http://hl7.org/fhir/condition-clinical version 3.0.1
Usages(none)

Mapping from ProbleemStatusCodelijst to Condition Clinical Status Codes

ACTIVE. Published on ?ngen-10? by Nictiz (Nictiz: https://www.nictiz.nl ). CC0

Maps the HCIM ConcernForTransfer release 2017 terminology for ProblemStatus to the FHIR STU3 terminology associated with Condition.clinicalStatus .


Group 1 Mapping from http://hl7.org/fhir/condition-clinical|http://hl7.org/fhir/condition-clinical version 3.0.1 to unspecified code system

Source Code Relationship Target Code Comment
55561003 (Active) is equal to active
55561003 (Active) has specialization recurrence When problem is recurring, it is active, but recurrence also tells you there has been a period of inactivity before. Recurrence thus provides more context than just 'active'.
73425007 (Inactive) is equal to inactive
73425007 (Inactive) has specialization remission When problem is in remission, it is considered inactive, but remission gives more context on the expectation of the problem returning. Remission thus provides more context than just 'inactive'.
73425007 (Inactive) has specialization resolved When problem is resolved, it is considered inactive, but resolved gives more context on the expectation of the problem returning. Resolved thus provides more context than just 'inactive'.

Produced 08 Sep 2023