mCODE FHIR Examples

This section provides some examples how mCODE elements may be represented in a FHIR instance which conforms to this implementation guide.

• Patient: mCODEPatientExample01 and mCODEPatientExample02 shows patient demographics like name, address, race, and ethnicity.
• Primary Cancer Condition: mCODEPrimaryCancerConditionExample01 shows an example for a patient diagnosed with non-small cell lung cancer (NSCLC) adenocarcinoma.
• Secondary Cancer Condition: mCODESecondaryCancerConditionExample01 shows an example for a patient diagnosed with secondary malignant neoplasm of the brain.
• Cancer Disease Status: mCODECancerDiseaseStatusExample01 shows an example for a patient whose cancer disease status is improving.
• Clinical Staging Classification: mCODETNMClinicalStageGroupExample01, mCODETNMClinicalPrimaryTumorCategoryExample01, mCODETNMClinicalRegionalNodesCategoryExample01 and mCODETNMClinicalDistantMetastasesCategoryExample01 specify the clinical T, N, and M categories for mCODEPrimaryCancerConditionExample01.
• Pathological Staging Classification: mCODETNMPathologicalStageGroupExample01, mCODETNMPathologicalPrimaryTumorCategoryExample01, mCODETNMPathologicalRegionalNodesCategoryExample01 and mCODETNMPathologicalDistantMetastasesCategoryExample01 specify the pathologic T, N, and M categories for mCODEPrimaryCancerConditionExample01.
• Comorbid Condition: mCODEComorbidConditionExample01 shows an example for a patient diagnosed with Type 2 Diabetes Mellitus.
• ECOG Performance Status: mCODEECOGPerformanceStatusExample01 shows an example for a patient with an ECOG Performance Status of 1.
• Karnofsky Performance Status: mCODEKarnofskyPerformanceStatusExample01 shows an example for a patient with a Karnofsky Performance Status of 80.
• Cancer Related Surgical Procedure: mCODECancerRelatedSurgicalProcedureExample01 shows an example for a patient who underwent a partial lobectomy of the lung for cancer treatment.
• Cancer Related Radiation Procedure: mCODECancerRelatedRadiationProcedureExample01 shows an example for a patient who went underwent brachytherapy for cancer treatment.
• Tumor Marker: mCODETumorMarkerExample01 shows a simple example of an EGFR tumor marker status as positive.
• Genomics Report: mCODECancerGenomicsReportExample01 shows a very small subset elements found in a genomics report which include the test service and test name.
• Genetic Variant: mCODECancerGeneticVariantFoundExample01 extends the contents of the Genomics Report by showing the results of a variant found for a specific gene, STK-11. This example differs from the mutation test result in that there was no preconceived test for a specific variant ahead of time. Rather, it is the result of any variants found for a given DNA region.
• Genetic Variant - single somatic mutation: mCODECancerGeneticVariantExample02 extends the contents of the Genomic Report example showing whether a test for a specific mutation for BRCA1 was present.

Additional Notes

• The narrative rendering of the FHIR examples may not exactly match the wording or order of the structured portion of the FHIR examples. This is on purpose since it is allowed for an implementation to present the data in a way that is understandable to the end user so long as the meaning and context of the structured and coded content is preserved.
• The narrative rendering might also contain data not explicitly appearing in the structured section of the FHIR example. In this case, rather than including contained resources, our example assumes this content is generated implicitly by the backend application retrieving and parsing data from the FHIR references included in the structured section of the example. For example, in mCODEGenomicsReportExample01, the narrative section contains information about the genetic mutation tested and variant found, however the coded section just includes the external references to each.
• The FHIR examples conform to the HL7 FHIR Argonaut IG where applicable and is subject to change with subsequent releases.
• Proprietary content like AJCC staging categories may appear in some of these examples solely for the purposes of illustration only. It is expected that all implementers will adhere to licensing requirements as appropriate.