Reporting Cancer Cases to Public Health Agencies

Type	Standard / Implementation Specification	Standards Process Maturity	Implementation Maturity	Federally required	Cost	Test Tool Availability
Implementation Specification	Implementation Guide for Ambulatory Healthcare Provider Reporting to Central Cancer Registries, August 2012	Final	Production	Yes	Free	Yes
Implementation Specification	HL7 CDA ® Release 2 Implementation Guide: Reporting to Public Health Cancer Registries from Ambulatory Healthcare Providers, Release 1, DSTU Release 1.1 – US Realm	Balloted Draft	Production	Yes	Free	Yes
Implementation Specification	North American Association of Central Cancer Registries, Inc. (NAACCR), Standards for Cancer Registries, Volume V, Pathology Laboratory Electronic Reporting, Version 4.0, published April 2011	Final	Production	Yes	Free	Yes Yes
Emerging Implementation Specification	IHE Quality, Research, and Public Health Technical Framework Supplement, Structured Data Capture, Trial Implementation	Balloted Draft	Pilot	No	Free	No

Limitations, Dependencies, and Preconditions for Consideration	Applicable Security Patterns for Consideration
Stakeholders should refer to the health department in their state or local jurisdiction to determine onboarding procedures, obtain a jurisdictional implementation guide if applicable, and determine which transport methods are acceptable for submitting cancer reporting date as there may be jurisdictional variation or requirements. Some jurisdictions may not support cancer case reporting at this time. Note that the NAACCR specification listed has not been vetted through a Voluntary Consensus Standards Body (VSCB), however it references the HL7 V 2.5.1 standard and LOINC, and has been sponsored by a number of organizations working in the cancer registry space. See CDA and IHE projects in the Interoperability Proving Ground.	Secure Communication – create a secure channel for client-to-server and server-to-server communication. Secure Message Router – securely route and enforce policy on inbound and outbound messages without interruption of delivery. Authentication Enforcer – centralized authentication processes. Authorization Enforcer – specifies access control policies. Credential Tokenizer – encapsulate credentials as a security token for reuse (e.g., – SAML, Kerberos). Assertion Builder – define processing logic for identity, authorization and attribute statements. User Role – identifies the role asserted by the individual initiating the transaction. Purpose of Use - Identifies the purpose for the transaction.

Limitations, Dependencies, and Preconditions for Consideration

Applicable Security Patterns for Consideration

Stakeholders should refer to the health department in their state or local jurisdiction to determine onboarding procedures, obtain a jurisdictional implementation guide if applicable, and determine which transport methods are acceptable for submitting cancer reporting date as there may be jurisdictional variation or requirements. Some jurisdictions may not support cancer case reporting at this time.
Note that the NAACCR specification listed has not been vetted through a Voluntary Consensus Standards Body (VSCB), however it references the HL7 V 2.5.1 standard and LOINC, and has been sponsored by a number of organizations working in the cancer registry space.
See CDA and IHE projects in the Interoperability Proving Ground.

Secure Communication – create a secure channel for client-to-server and server-to-server communication.
Secure Message Router – securely route and enforce policy on inbound and outbound messages without interruption of delivery.
Authentication Enforcer – centralized authentication processes.
Authorization Enforcer – specifies access control policies.
Credential Tokenizer – encapsulate credentials as a security token for reuse (e.g., – SAML, Kerberos).
Assertion Builder – define processing logic for identity, authorization and attribute statements.
User Role – identifies the role asserted by the individual initiating the transaction.
Purpose of Use - Identifies the purpose for the transaction.

Comment