IDEA4RC FHIR Implementation Guide
1.0.0 - release 150

This page is part of the IDEA4RC FHIR Implementation Guide (v1.0.0: QA Preview) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version. For a full list of available versions, see the Directory of published versions

Episode Event Model to this guide Map

Mapping from Episode Event to Condition: Primary Cancer

Source CodeCard.RelationshipTarget CodeCard.Comment
EpisodeEvent.cancerEpisodeReference1..*is related toCondition.extension:condition-occurredFollowing0..*If not 'Baseline'
EpisodeEvent.cancerEpisodeReference1..*is related toCondition0..*If 'Baseline': new Condition
EpisodeEvent.diseaseStatus1..*is equivalent toCondition.clinicalStatus.coding:athena0..1The eventType is recoded in the coding athena slice, however the type has to be consistent with the combination of status / previous status and existance of previous Condition resources. The clincalStatus has in fact a required binding with http://hl7.org/fhir/R4/valueset-condition-clinical.html. active | recurrence | relapse | inactive | remission | resolved. For example Stable disease - 32948 may have status='active' and extension:condition-occurredFollowing.exists(), Complete Remission may have status='inactive' and extension:condition-occurredFollowing.exists(); Recurrence - 2000100002 may have status.: 'recurrence' and extension:condition-occurredFollowing.exists(). Progression - 32949 may have status='relapse' and extension:condition-occurredFollowing.exists().
EpisodeEvent.definedAt0..*is related toCondition.extension:sameHospital0..1Temporary included in the guide for covering the request of tracking if this information has been captured and maintained by the same or other organizations. It is envisioned that this kind of requirements could be covered by recording where specific act are taking place.
EpisodeEvent.dateOfEpisode1..*is equivalent toCondition.onset[x]0..1If it is when this particular Condition record was created in the system