Central Cancer Registry Reporting Content IG
0.1.0 - STU 1 Ballot

This page is part of the Making EHR Data MOre available for Research and Public Health (MedMorph) Central Cancer Registry Reporting Content IG (v0.1.0: STU 1 Ballot 1) based on FHIR R4. . For a full list of available versions, see the Directory of published versions

Artifacts Summary

Contents:

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Behavior: Capability Statements

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.

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide

Central Cancer Registry Report Content Bundle

Bundle Resource profile for exchanging the clinical content of a Cancer Report to a Central Cancer Registry. This bundle is always part of the Central Cancer Registry Reporting Bundle.
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.
US Public Health Encounter

This Encounter profile represents the encounter related to the event. It is based on the US Core Encounter.
US Public Health Patient

This Patient profile represents a US Public Health Patient.

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:

  • contact detail (e.g. a telephone number or an email address)
  • a communication language
  • a race
  • an ethnicity
  • a birth sex
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.
CancerPatient

Patient Resource profile for Central Cancer Registry Reporting based off the US Public Health Patient profile with further restrictions on identifiers.

Structures: Extension Definitions

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

Terminology: Value Sets

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.

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like

Patient - Example

An example showing a Patient
Encounter - Example

An example showing an Encounter
PHA Organization - Example

An example showing a PHA Organization
Healthcare Organization - Example

An example showing a Health Care Organization
Reporting Bundle - Example

An example showing a Reporting Bundle
Content Bundle - Example

An example showing a Cancer Content Bundle
Specifiation Bundle - Example

An example showing a Central Cancer Registry Reporting Specification Bundle
PlanDefinition - Example

An example showing a Central Cancer Registry Reporting PlanDefinition instance
PHA Endpoint - Example

An example showing an PHA Endpoint
Healthcare Organization Endpoint - Example

An example showing an Healthcare Organization Endpoint