Details
-
Comment
-
Resolution: Considered - No action required
-
Medium
-
US Core (FHIR)
-
4.1.0 [deprecated]
-
Cross-Group Projects
-
US Core Laboratory Result Observation Profile
US Core Observation Clinical Test Result Profile [deprecated]
US Core Observation Imaging Result Profile [deprecated]
US Core Observation SDOH Assessment Profile [deprecated]
US Core Observation Sexual Orientation Profile
US Core Observation Social History Profile [deprecated]
US Core Observation Survey Profile [deprecated] -
Artifacts Summary
-
Description
Reference: variance request from mCODE: FHIR-30707
We received a variance in mCODE for an Observation – disease status. CodexRT's RadiotherapyDiseaseStatus the mCODE CancerDiseaseStatus profile within CodexRT STU1. The CodexRT profile just elaborates the mCODE profile slightly with a bit more detail. There is no USCore4 profile that serves as a suitable base for this Observation.
CodexRT depends on mCODE STU2 which is based on USCore 4.1.0, so CodexRT requires the same variance that was granted to mCODE.
On the bright side, CodexRT depends on mCODE. The next version of mCODE will base this observation on USCoreClinicalTestResultProfile when it moves to a USCOre5.0.1 base (see https://build.fhir.org/ig/HL7/fhir-mCODE-ig/StructureDefinition-mcode-cancer-disease-status.html), and CodexRT will follow along post-STU1.
So, this variance request is for CodexRT STU1 (based on mCODE STU2, based on USCore4), and should go away once mCODE (and CodexRT) move to a USCore5 base.
The STU1 version of CodexRT is based on the the STU2 version of mCODE that is based on USCore 4.1.0 (see http://hl7.org/fhir/us/mcode/StructureDefinition-mcode-cancer-disease-status.html), so DiseaseStatus is based on Observation.
So, CodexRT will require a variance for STU1.
