This page is part of the Making EHR Data MOre available for Research and Public Health (MedMorph) Central Cancer Registry Reporting Content IG (v1.0.0: STU1) 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
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
Central Cancer Registry Reporting EHR Capability Statement |
This profile defines the expected capabilities of the ‘‘EHR’’ actor when conforming to the Central Cancer Registry Reporting Content IG. This role is responsible for allowing creation, modification and deletion of Subscriptions and allows searching and retrieval of resources using US Core APIs. |
These define constraints on FHIR resources for systems conforming to this implementation guide.
Cancer Encounter |
This Encounter profile represents the encounter related to the cancer event. It is based on the US Core Encounter. |
CancerPatient |
Patient Resource profile for Central Cancer Registry Reporting based off the US Public Health Patient profile with further restrictions on identifiers. |
Central Cancer Registry Report Composition |
This Composition profile is used to organize the central cancer registry report content. |
Central Cancer Registry Reporting Bundle |
Bundle Resource profile for exchanging a cancer report with the Central Cancer Registry. This bundle contains the MessageHeader resource used for routing and the Content Bundle specifying the content. |
Central Cancer Registry Reporting Content Bundle |
This profile is used to represent the Central Cancer Registry Report Content. The content bundle is represented using a bundle of type Document using the Composition resource. |
Central Cancer Registry Reporting Message Header |
This is the MessageHeader Resource profile for the IG. |
Central Cancer Registry Reporting PlanDefinition |
This PlanDefinition profile defines the logic and rules around determining: whether or not a condition is reportable to a cancer registry, which jurisdiction(s) is/are responsible, which jurisdiction(s) need to be notified, and if the cancer condition is reportable, gives timing information, next steps and condition information to the clinician. The rules for determining reportability described by the Central Cancer Registry Reporting specification involve the use of triggering codes to determine potentially reportable events, and optionally locally evaluated rules for determining suspected reportable events. |
Central Cancer Registry Reporting Primary Cancer Condition |
This is the Primary Cancer Condition Resource profile for the IG. |
US Public Health Patient |
This Patient profile represents a US Public Health Patient. This proile is present in the IG to synchronize with common Patient profile being developed by public health profiles library IG. This profile is being used by the Cancer Patient profile. Implementers of the IG are expected to implement only the Cancer Patient profile. It is based on the US Core Patient profile with further restrictions to allow masking of some data elements and the addition of the patient-genderIdentity extension. For ONC’s USCDI requirements, it adds Must Support constraints to the following:
|
These define constraints on FHIR data types for systems conforming to this implementation guide.
US Public Health Tribal Affiliation Extension |
This Extension profile represents an affiliated tribe name and whether or not the patient is an enrolled member |
These define sets of codes used by systems conforming to this implementation guide.
Cancer Core Reportability Codes |
The valueset contains SNOMED-CT and ICD-10-CM codes for Cancer Core Reportability determination. These are just sample codes and the actual value set will be published by the Central Cancer Registry. |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
Allergy Intolerance - Example |
An example showing an Allergy Intolerance |
Cancer Encounter - Example |
An example showing a Cancer Encounter |
Cancer Patient - Example |
An example showing a Cancer Patient |
Cancer Related Medication Administration - Example |
An example showing a Cancer-related MedicationAdministration |
Central Cancer Registry Endpoint - Example |
An example showing an Central Cancer Registry Endpoint |
Central Cancer Registry PlanDefinition - Example |
An example showing a Central Cancer Registry Reporting PlanDefinition instance |
Central Cancer Registry Reporting Bundle - Example |
An example showing a Central Cancer Registry Reporting Bundle |
Central Cancer Registry Reporting Composition - Example |
An example showing a Central Cancer Registry Reporting Composition resource |
Central Cancer Registry Reporting Content Bundle - Example |
An example showing a Central Cancer Registry Reporting Content Bundle |
Central Cancer Registry Reporting Message Header - Example |
An example showing a Central Cancer Registry Reporting Message Header resource |
Central Cancer Registry Reporting Primary Cancer Condition - Example |
An example showing a CCRR Primary Cancer Condition |
Central Cancer Registry Reporting Specifiation Bundle (Knowledge Artifact)- Example |
An example showing a Central Cancer Registry Reporting Specification Bundle (Knowledge Artifact) |
Healthcare Organization - Example |
An example showing a Health Care Organization |
Healthcare Organization Endpoint - Example |
An example showing an Healthcare Organization Endpoint |
PHA Organization - Example |
An example showing a PHA Organization |
Practitioner - Example |
An example showing a Practitioner |
mCODE Cancer Stage Group - Example |
An example showing an mCODE Cancer Stage Group |
mCODE Radiotherapy Course Summary - Example |
An example showing an mCODE Radiotherapy Course Summary |
mCODE Radiotherapy Lymph Nodes Treatment Volume - Example |
An example showing an mCODE Radiotherapy Volume |
mCODE Radiotherapy Volume - Example |
An example showing an mCODE Radiotherapy Volume |
mCODE TNM Clinical Distant Metastases Category - Example |
An example showing an mCODE TNM Clinical Distant Metastases Category |
mCODE TNM Clinical Primary Tumor Category - Example |
An example showing an mCODE TNM Clinical Primary Tumor Category |
mCODE TNM Clinical Regional Nodes Category - Example |
An example showing an mCODE TNM Clinical Regional Nodes Category |