Central Cancer Registry Reporting Content IG
2.0.0-ballot - STU 2 Ballot

Central Cancer Registry Reporting Content IG - Downloaded Version 2.0.0-ballot See the Directory of published versions

## Useful Downloads

Page standards status: Informative

### Download

You can also download:

- this entire guide
- the definition resources in json, xml, ttl, or csv format, or
- the example resources in json, xml or ttl format.

#### Expansion Params

Parameter | Value
--- | ---
system-version | SNOMED CT[US]

#### Cross Version Analysis

This is an R4 IG. None of the features it uses are changed in R4B, so it can be used as is with R4B systems. Packages for both R4 (hl7.fhir.us.central-cancer-registry-reporting.r4) and R4B (hl7.fhir.us.central-cancer-registry-reporting.r4b) are available.

#### Dependency Table

IG | Package | FHIR | Comment
--- | --- | --- | ---
Central Cancer Registry Reporting Content IG | hl7.fhir.us.central-cancer-registry-reporting#2.0.0-ballot | R4 |
HL7 Terminology (THO) | hl7.terminology.r4#7.0.1 | R4 | Automatically added as a dependency - all IGs depend on HL7 Terminology
FHIR Extensions Pack | hl7.fhir.uv.extensions.r4#5.2.0 | R4 |
US Core Implementation Guide | hl7.fhir.us.core#6.1.0 | R4 |
HL7 Terminology (THO) | hl7.terminology.r4#5.0.0 | R4 |
FHIR Extensions Pack | hl7.fhir.uv.extensions.r4#1.0.0 | R4 |
Bulk Data Access IG | hl7.fhir.uv.bulkdata#2.0.0 | R4 |
SMART App Launch | hl7.fhir.uv.smart-app-launch#2.1.0 | R4 |
VSAC | us.nlm.vsac#0.11.0 | R4 |
Structured Data Capture | hl7.fhir.uv.sdc#3.0.0 | R4 |
PHINVads | us.cdc.phinvads#0.12.0 | R4 |
IHE FormatCode Vocabulary | ihe.formatcode.fhir#1.1.0 | R4 |
US Public Health Profiles Library | hl7.fhir.us.ph-library#1.0.0 | R4 |
US Core Implementation Guide | hl7.fhir.us.core#5.0.1 | R4 |
HL7 Terminology (THO) | hl7.terminology.r4#3.1.0 | R4 |
SMART App Launch | hl7.fhir.uv.smart-app-launch#2.0.0 | R4 |
VSAC | us.nlm.vsac#0.7.0 | R4 |
Subscriptions R5 Backport | hl7.fhir.uv.subscriptions-backport.r4#1.1.0 | R4 |
minimal Common Oncology Data Elements (mCODE) Implementation Guide | hl7.fhir.us.mcode#4.0.0 | R4 |
HL7 Terminology (THO) | hl7.terminology.r4#6.2.0 | R4 |
Genomics Reporting Implementation Guide | hl7.fhir.uv.genomics-reporting#2.0.0 | R4 |
Cancer Pathology Data Sharing | hl7.fhir.us.cancer-reporting#2.0.0 | R4 |
HL7 Terminology (THO) | hl7.terminology.r4#6.5.0 | R4 |
HL7 FHIR Profile: Occupational Data for Health (ODH), Release 1, STU 1.3 (Standard for Trial Use) | hl7.fhir.us.odh#1.3.0 | R4 |
SMART App Launch | hl7.fhir.uv.smart-app-launch#2.2.0 | R4 |
HL7 Terminology (THO) | hl7.terminology#5.5.0 | R4 |
FHIR Tooling Extensions IG | hl7.fhir.uv.tools.r4#0.8.0 | R4 | for example references

Package hl7.fhir.uv.extensions.r4#5.2.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Mon, Feb 10, 2025 21:45+1100+11:00)

Package hl7.fhir.uv.extensions.r4#1.0.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00)

Package hl7.fhir.uv.bulkdata#2.0.0 FHIR based approach for exporting large data sets from a FHIR server to a client application (built Fri, Nov 26, 2021 05:56+1100+11:00)

Package hl7.fhir.uv.sdc#3.0.0 The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR. This includes two components: * Support more sophisticated questionnaire/form use-cases such as those needed for research, oncology, pathology and other clinical domains. *Support pre-population and auto-population of EHR data into forms/questionnaires for uses outside direct clinical care (patient safety, adverse event reporting, public health reporting, etc.). (built Tue, Mar 8, 2022 18:36+0000+00:00)

Package ihe.formatcode.fhir#1.1.0 Implementation Guide for IHE defined FormatCode vocabulary. (built Thu, Feb 24, 2022 16:55-0600-06:00)

Package hl7.fhir.us.core#6.1.0 The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum conformance requirements for accessing patient data. The Argonaut pilot implementations, ONC 2015 Edition Common Clinical Data Set (CCDS), and ONC U.S. Core Data for Interoperability (USCDI) v1 provided the requirements for this guide. The prior Argonaut search and vocabulary requirements, based on FHIR DSTU2, are updated in this guide to support FHIR Version R4. This guide was used as the basis for further testing and guidance by the Argonaut Project Team to provide additional content and guidance specific to Data Query Access for purpose of ONC Certification testing. These profiles are the foundation for future US Realm FHIR implementation guides. In addition to Argonaut, they are used by DAF-Research, QI-Core, and CIMI. Under the guidance of HL7 and the HL7 US Realm Steering Committee, the content will expand in future versions to meet the needs specific to the US Realm. These requirements were originally developed, balloted, and published in FHIR DSTU2 as part of the Office of the National Coordinator for Health Information Technology (ONC) sponsored Data Access Framework (DAF) project. For more information on how DAF became US Core see the US Core change notes. (built Fri, Jun 30, 2023 14:02+0000+00:00)

Package hl7.fhir.us.core#5.0.1 The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum conformance requirements for accessing patient data. The Argonaut pilot implementations, ONC 2015 Edition Common Clinical Data Set (CCDS), and ONC U.S. Core Data for Interoperability (USCDI) v1 provided the requirements for this guide. The prior Argonaut search and vocabulary requirements, based on FHIR DSTU2, are updated in this guide to support FHIR Version R4. This guide was used as the basis for further testing and guidance by the Argonaut Project Team to provide additional content and guidance specific to Data Query Access for purpose of ONC Certification testing. These profiles are the foundation for future US Realm FHIR implementation guides. In addition to Argonaut, they are used by DAF-Research, QI-Core, and CIMI. Under the guidance of HL7 and the HL7 US Realm Steering Committee, the content will expand in future versions to meet the needs specific to the US Realm. These requirements were originally developed, balloted, and published in FHIR DSTU2 as part of the Office of the National Coordinator for Health Information Technology (ONC) sponsored Data Access Framework (DAF) project. For more information on how DAF became US Core see the US Core change notes. (built Wed, Jun 22, 2022 19:44+0000+00:00)

Package hl7.fhir.uv.subscriptions-backport.r4#1.1.0 The Subscription R5 Backport Implementation Guide enables servers running versions of FHIR earlier than R5 to implement a subset of R5 Subscriptions in a standardized way. (built Wed, Jan 11, 2023 15:34+1100+11:00)

Package hl7.fhir.uv.genomics-reporting#2.0.0 Guidelines for reporting of clinical genomics results using HL7 FHIR. (built Mon, May 9, 2022 16:52+0000+00:00)

Package hl7.fhir.us.mcode#4.0.0 mCODE™ (short for Minimal Common Oncology Data Elements) is an initiative intended to assemble a core set of structured data elements for oncology electronic health records. (built Sun, Feb 16, 2025 19:03+0000+00:00)

Package hl7.fhir.us.cancer-reporting#2.0.0 This implementation guide (IG) provides Health Level Seven (HL7 FHIR) resources to define standards for cancer pathology information exchange from a hospital or facility-based laboratory information system (LIS) to a hospital or facility-based electronic health record (EHR) system or to a central cancer registry. When sending between LIS and EHR systems, implementors may choose to use transport and processing modalities, such as FHIR bundles. This publication provides the data model, defined data items and their corresponding code and value sets specific to a cancer pathology synoptic report. This guide contains a library of FHIR profiles to create a cancer pathology bundle and is compliant with FHIR Release 4. (built Fri, Oct 3, 2025 14:09+0000+00:00)

Package hl7.fhir.us.odh#1.3.0 HL7 FHIR Profile: Occupational Data for Health (ODH), Release 1.3 (Standard for Trial Use) This Implementation Guide is a reconciled version, containing changes in response to comments received in the Sept. 2018 ballot. It has been updated to FHIR R4.0.1. Introduction and Guidance This Implementation Guide (IG) contains profiles to implement support for Occupational Data for Health (ODH). ODH describes structured work information primarily designed to facilitate clinical care, including population health and value-based care. ODH also can be used to support public health reporting. ODH is not designed to support billing activities. This set of FHIR profiles is specified as a composition resource, but it is not intended to be used as a stand-alone composition. Rather, the desired content should be included in broader IGs and available as a response to requests for ODH information. Some use cases may leverage only a subset of the ODH profiles, and these should be specified within those work products. For instance, in the Vital Records Death Reporting (VRDR) IG, the data requirements for work information are limited to those in the Usual Work profile. While this profile is specified for the US Realm, the design is intended to also support international needs. Three of the referenced value sets—Occupation, Industry, and Supervisory Level— are necessarily US specific. The remaining three value sets—Work Schedule, Employment Status, and Work Classification—use international concepts. Input is requested regarding whether these should be specified as ‘extensible’, ‘required’ (using ‘text only’ where a concept does not yet exist such as a new occupation), or as an ‘example’ for those US specific concepts. Background The majority of adults in the U.S. spend more than half their waking hours at work. Therefore, health and work are inextricably inter-related. For example, the management of chronic conditions requires taking the patient’s work environment into consideration. Work-related conditions are often first brought to the attention of a primary care provider. Some conditions related to exposure to hazards in the workplace can have a long latency, requiring knowledge of a person’s work history for recognition, diagnosis, and treatment. The recognition of new conditions related to previously unknown workplace hazards has often come from astute clinicians, which requires knowledge of the patient’s work. ONC has indicated recognition of the value of work information for health care. The incorporation of ODH into Electronic Health Records (EHRs) and other health IT systems presents an opportunity to improve health in relation to work. ODH provides a structure and standardization for work information that can be used across systems to take advantage of system tools for clinical decision support, population health, and public health. Research has been conducted and guidance is available to support clinicians, and the use of ODH by health IT systems can support identification of patients that would benefit the most from this knowledge. Scope The Occupational Data for Health (ODH) FHIR IG covers information about a patient’s work, including some voluntary work, or a patient’s household members’ work. ODH is designed for the social history section of a medical record, to facilitate clinical care in multiple disciplines and delivery environments. ODH can be used for clinical decision support, population health activities and value-based care, and public health reporting. The scope of the work information in ODH includes: • Employment Status • Retirement Date • Combat Zone Period • Past or Present Job for the patient or a household member, which includes: o Past or Present Job Occupation o Past or Present Job Industry o Work Classification o Work Schedule, which includes:
    - Weekly Work Days

    - Daily Work Hours
o Job Duty o Occupational Hazard o Employer name o Employer address o Related Subject (when it is Past or Present Job of a household member of the person) o Start/End Dates • Usual Work of the patient or a household member, which includes: o Usual Occupation o Usual Industry o Usual Occupation Duration o Related Subject (when it is Usual Work of a household member of the person) o Start Date Known Issues and Limitations This IG includes more extensive occupational data than typically collected in current systems. The content and structure of this IG is intended to inform clinical care, support population health, and contribute to public health activities. While there may be some overlap with administrative and billing information maintained by some systems, the information in this IG is not designed to support billing and administrative needs. While multiple retirement dates are supported, the retirement date is not linked to any specific job, or usual occupation. Credits Co-Editor: Lori Reed-Fourquet e-HealthSign, LLC lfourquet@ehealthsign.com Co-Editor: Rob Hausam Hausam Consulting rob@hausamconsulting.com Co-Editor: Mark Kramer MITRE Corporation mkramer@mitre.org This set of FHIR profiles was produced and developed through the efforts of a project of the National Institute of Occupational Safety and Health (NIOSH), the U.S. federal agency responsible for conducting research and making recommendations for the prevention of work-related injury and illness. NIOSH is a part of the U.S. Centers for Disease Control and Prevention (CDC). NIOSH consulted stakeholders in clinical care, public health, health IT, health informatics and U.S. government agencies to develop ODH. The HL7® Public Health and Emergency Response Work Group sponsored development of this set of FHIR profiles. Co-sponsoring HL7® Work Groups were Orders and Observations (OO), Patient Administration (PA), and Clinical Quality Initiative (CQI). The following individuals provided subject matter expertise for this set of FHIR profiles: Genevieve Barkocy Luensman, NIOSH; Eileen Storey, Professional Services Partners, formerly NIOSH; Margaret S. Filios, NIOSH; Christina Socias-Morales, NIOSH; Lauren Brewer, NIOSH; Barbara Wallace, Professional Services Partners. Authors Name Email/URL HL7 International - Public Health http://www.hl7.org/Special/committees/pher (built Wed, Mar 22, 2023 12:13+1100+11:00)

Package hl7.fhir.uv.tools.r4#0.8.0 This IG defines the extensions that the tools use internally. Some of these extensions are content that are being evaluated for elevation into the main spec, and others are tooling concerns (built Tue, Aug 5, 2025 20:09+1000+10:00)

#### Globals Table

There are no Global profiles defined

#### IP Statements

This publication includes IP covered under the following statements.

- ISO maintains the copyright on the country codes, and controls its use carefully. For further details see the ISO 3166 web page: https://www.iso.org/iso-3166-country-codes.html
  Show Usage
  - ISO 3166-1 Codes for the representation of names of countries and their subdivisions — Part 1: Country code: Bundle/central-cancer-registry-reporting-specification-bundle-example, CancerCoreReportabilityCodes... Show 13 more, CancerStatusEvidenceType, CcrrComposition, CentralCancerRegistryReporting, CentralCancerRegistryReportingBundle, CentralCancerRegistryReportingContentBundle, CentralCancerRegistryReportingEHRCapabilityStatement, CentralCancerRegistryReportingEncounter, CentralCancerRegistryReportingExample, CentralCancerRegistryReportingMessageHeader, CentralCancerRegistryReportingOrganization, CentralCancerRegistryReportingPatient, CentralCancerRegistryReportingPlanDefinition and CentralCancerRegistryReportingPrimaryCancerCondition
- Most of the information on the CDC and ATSDR websites is not subject to copyright, is in the public domain, and may be freely used or reproduced without obtaining copyright permission.For information and exceptions regarding use of CDC material please see https://www.cdc.gov/other/agencymaterials.html.
  Show Usage
  - CDC Race and Ethnicity: Patient/example
- The UCUM codes, UCUM table (regardless of format), and UCUM Specification are copyright 1999-2009, Regenstrief Institute, Inc. and the Unified Codes for Units of Measures (UCUM) Organization. All rights reserved. https://ucum.org/trac/wiki/TermsOfUse
  Show Usage
  - Unified Code for Units of Measure (UCUM): Bundle/ccrr-non-encounter-based-content-bundle-example, MedicationAdministration/cancer-med-admin-docetaxel-example and Observation/odh-usual-work
- This material contains content from LOINC. LOINC is copyright © 1995-2020, Regenstrief Institute, Inc. and the Logical Observation Identifiers Names and Codes (LOINC) Committee and is available at no cost under the license. LOINC® is a registered United States trademark of Regenstrief Institute, Inc.
  Show Usage
  - LOINC: Bundle/ccrr-content-bundle-example, Bundle/ccrr-encounter-based-content-bundle-example... Show 9 more, Bundle/ccrr-non-encounter-based-content-bundle-example, Bundle/reporting-bundle-example, CcrrComposition, Composition/ccrr-composition-example, Observation/cancer-stage-group-example, Observation/non-smoker, Observation/odh-usual-work, Observation/tnm-clinical-primary-tumor-category-cT2 and Observation/tnm-clinical-regional-nodes-category-cN0
- This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/get-snomed or info@snomed.org.
  Show Usage
  - SNOMED Clinical Terms&reg; (SNOMED CT&reg;): Bundle/ccrr-content-bundle-example, Bundle/ccrr-encounter-based-content-bundle-example... Show 18 more, Bundle/ccrr-non-encounter-based-content-bundle-example, Bundle/reporting-bundle-example, CancerCoreReportabilityCodes, CancerStatusEvidenceType, CcrrComposition, Composition/ccrr-composition-example, Condition/primary-cancer-condition-breast, Encounter/encounter-cancer-example, Encounter/encounter-cancer-example-radiation, Encounter/encounter-cancer-example-surgery, MedicationAdministration/cancer-med-admin-docetaxel-example, Observation/cancer-stage-group-example, Observation/non-smoker, Observation/tnm-clinical-distant-metastases-category-cM0, Observation/tnm-clinical-primary-tumor-category-cT2, Observation/tnm-clinical-regional-nodes-category-cN0, Procedure/cancer-related-surgical-procedure-lumpectomy and Procedure/radiotherapy-example
- This material derives from the HL7 Terminology (THO). THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html
  Show Usage
  - Condition Category Codes: Bundle/ccrr-content-bundle-example, Bundle/ccrr-encounter-based-content-bundle-example... Show 4 more, Bundle/ccrr-non-encounter-based-content-bundle-example, CentralCancerRegistryReportingPrimaryCancerCondition, Condition/primary-cancer-condition-breast and Condition/problem-list-diabetes
  - Condition Clinical Status Codes: Bundle/ccrr-content-bundle-example, Bundle/ccrr-encounter-based-content-bundle-example, Bundle/ccrr-non-encounter-based-content-bundle-example, Condition/primary-cancer-condition-breast and Condition/problem-list-diabetes
  - ConditionVerificationStatus: Bundle/ccrr-content-bundle-example, Bundle/ccrr-encounter-based-content-bundle-example, Bundle/ccrr-non-encounter-based-content-bundle-example, Condition/primary-cancer-condition-breast and Condition/problem-list-diabetes
  - Endpoint Connection Type: HealthCareSenderAndReceiver and PHAReceiver
  - Observation Category Codes: Bundle/ccrr-content-bundle-example, Observation/cancer-stage-group-example... Show 4 more, Observation/non-smoker, Observation/tnm-clinical-distant-metastases-category-cM0, Observation/tnm-clinical-primary-tumor-category-cT2 and Observation/tnm-clinical-regional-nodes-category-cN0
  - PlanDefinitionType: Bundle/central-cancer-registry-reporting-specification-bundle-example, CentralCancerRegistryReportingExample and CentralCancerRegistryReportingPlanDefinition
  - identifierType: Patient/example
  - ActCode: Encounter/encounter-cancer-example, Encounter/encounter-cancer-example-radiation and Encounter/encounter-cancer-example-surgery
  - MaritalStatus: Patient/example
  - ParticipationType: CentralCancerRegistryReportingEncounter and Encounter/encounter-cancer-example
- Using RxNorm codes of type SAB=RXNORM as this specification describes does not require a UMLS license. Access to the full set of RxNorm definitions, and/or additional use of other RxNorm structures and information requires a UMLS license. The use of RxNorm in this specification is pursuant to HL7's status as a licensee of the NLM UMLS. HL7's license does not convey the right to use RxNorm to any users of this specification; implementers must acquire a license to use RxNorm in their own right.
  Show Usage
  - RxNorm: Bundle/ccrr-non-encounter-based-content-bundle-example and MedicationAdministration/cancer-med-admin-docetaxel-example