Interoperability Need: Reporting Cancer Cases to Public Health Agencies

Interoperability Need: Reporting Cancer Cases to Public Health Agencies
Type	Standard/Implementation Specification	Standards Process Maturity	Implementation Maturity	Adoption Level	Federally Required	Cost	Test Tool Availability
1-Standard	HL7 Clinical Document Architecture (CDA®), Release 2.0, Final Edition	Final	Production		Yes	Free	No
2-Implementation Specification	HL7 Implementation Guide for CDA® Release 2: Reporting to Public Health Cancer Registries from Ambulatory Healthcare Providers, Release 1 - US Realm	Balloted Draft	Production		Yes	Free	Yes
*1-Emerging 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	Pilot		Yes	Free	No
*Emerging Implementation Specification*	IHE Quality, Research, and Public Health Technical Framework Supplement, Structured Data Capture, Trial Implementation	Balloted Draft	Pilot		No	Free	No
*Emerging Implementation Specification*	HL7 FHIR DSTU 2, Structured Data Capture (SDC) Implementation Guide	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 data as there may be jurisdictional variation or requirements. Some jurisdictions may not support cancer case reporting at this time. See CDA projects in the Interoperability Proving Ground.	Secure Communication – create a secure channel for client-to- serve 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 – specified policies access control. Credential Tokenizer – encapsulate credentials as a security token for reuse (e.g., – SAML, Kerberos). User Role – identifies the role asserted by the individual initiating the transaction. Purpose of Use - Identifies the purpose for the transaction.

No comments have been posted yet.

HealthIT.gov