Case Reporting to Public Health Agencies

Printer Friendly, PDF & Email
Type Standard Implementation/Specification Standards Process Maturity Implementation Maturity Adoption Level Federally required Cost Test Tool Availability
Implementation Specification
Balloted Draft
Pilot
Rating 1
No
Free
No
Implementation Specification
Balloted Draft
Production
Rating 4
Yes
Free
Yes
Implementation Specification
Final
Feedback requested
Rating 2
No
Free
Yes
Implementation Specification
Balloted Draft
Pilot
Rating 2
No
Free
Yes
Emerging Implementation Specification
Balloted Draft
Pilot
Rating 1
No
Free
No
Emerging Implementation Specification
Balloted Draft
Pilot
Rating 1
No
Free
No
Limitations, Dependencies, and Preconditions for Consideration Applicable Security Patterns for Consideration
  • Electronic case reporting involves reporting to State and/or Local jurisdictions and is not yet widespread.
  • Structured Data Capture Implementation Guide does not currently restrict vocabulary to standard vocabulary sets, and may require further implementation guidance for case reporting purposes. 
  • The IHE Quality, Research, and Public Health Technical Framework Supplement, Structured Data Capture, Trial Implementation Implementation Guide does not support automated initiation of sending of case reports. It can support manual entry into an electronic form as follow-up to an initial case report submission. 
  • Some additional implementation guides related to public health reporting follow. Reporting is often captured under a specialized registry with associated standards when not specified as a separate measure. These include:
  • Note that the maturity level of FHIR resources may vary. The FHIR Maturity Model and each of the levels is described on the HL7 wiki.
  • See FHIR 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.
  • FHIR Security Labels support compliance with laws, policies, and consent directives governing HIPAA PHI and specially protected information (SPI)