IDEA4RC FHIR Implementation Guide
0.1.0 - CI Build 150

IDEA4RC FHIR Implementation Guide, published by IDEA4RC Project. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7-eu/idea4rc/ and changes regularly. See the Directory of published versions

ConceptMap: Patient Follow up Model to this guide Map (Experimental)

Official URL: http://hl7.eu/fhir/ig/idea4rc/ConceptMap/followup2FHIR Version: 0.1.0
Draft as of 2024-11-12 Computable Name: Followup2FHIR

Patient Follow up Model to this guide Map

It shows how the Patient Follow up model is mapped into this guide

Generated Narrative: ConceptMap followup2FHIR

Mapping from Patient Follow Up to http://hl7.eu/fhir/ig/idea4rc/StructureDefinition//Bundle-eu-i4rc


Group 1 Mapping from Patient Follow Up to Encounter: IDEA4RC

Source CodeRelationshipTarget CodeComment
PatientFollowUp.patient (Patient)is equivalent toEncounter.subject
PatientFollowUp.statusAtLastFollowUp (Status at last follow-up)is related toEncounter.diagnosis.conditionTHE STATUS AS DESCRIBED IN THE MODEL IS MAPPED INTO A SEPARET OBSERVATION (see below) If intended as the diagnosis at the last follow up. use = $diagnosis-role#AD (AdmissionDiagnosis) Details in the referred Condition
PatientFollowUp.patientFollowUpDate (Patient Follow Up date)is related toEncounter.period.start
PatientFollowUp.newCancerDiagnosis (New cancer diagnosis)is related toEncounter.diagnosis.conditionWhere use = $diagnosis-role#DD (Discharge Diagnosis) Details in the referred Condition
PatientFollowUp.dateOfNewCancerDiagnosis (Date of new cancer diagnosis)is related toEncounter.diagnosis.conditionWhere use = $diagnosis-role#DD (Discharge Diagnosis) Details in the referred Condition
PatientFollowUp.newCancerTopography (New cancer topography)is related toEncounter.diagnosis.conditionWhere use = $diagnosis-role#DD (Discharge Diagnosis) Details in the referred Condition

Group 2 Mapping from Patient Follow Up to Condition: Primary Cancer

Source CodeRelationshipTarget CodeComment
PatientFollowUp.patient (Patient)is equivalent toCondition.subject
PatientFollowUp.statusAtLastFollowUp (Status at last follow-up)is equivalent toCondition.clinicalStatusTHE STATUS AS DESCRIBED IN THE MODEL IS MAPPED INTO A SEPARET OBSERVATION (see below) If intended as the diagnosis at the last follow up. use = $diagnosis-role#AD (AdmissionDiagnosis) Details in the referred Condition
PatientFollowUp.patientFollowUpDate (Patient Follow Up date)(not mapped)
PatientFollowUp.newCancerDiagnosis (New cancer diagnosis)is equivalent toCondition.codeParent Encounter.diagnosis with use = $diagnosis-role#DD (Discharge Diagnosis)
PatientFollowUp.dateOfNewCancerDiagnosis (Date of new cancer diagnosis)is equivalent toCondition.onSetDateTimeParent Encounter.diagnosis with use = $diagnosis-role#DD (Discharge Diagnosis). See the CancerEpisode map for further details about the representation of the date of diagnosis
PatientFollowUp.newCancerTopography (New cancer topography)is equivalent toCondition.bodySiteParent Encounter.diagnosis with use = $diagnosis-role#DD (Discharge Diagnosis)

Group 3 Mapping from Patient Follow Up to Observation: Status at the Last Follow Up

Source CodeRelationshipTarget Code
PatientFollowUp.patient (Patient)is equivalent toObservation.subject
PatientFollowUp.statusAtLastFollowUp (Status at last follow-up)is equivalent toObservation.valueCodeableConcept

Group 4 Mapping from Patient Follow Up to Observation: date of the last contact

Source CodeRelationshipTarget Code
PatientFollowUp.patient (Patient)is equivalent toObservation.subject
PatientFollowUp. (Patient Follow Up date)is equivalent toObservation.valueDateTime