1. HealthIT.gov
  • Print

Interoperability Need: Case Reporting to Public Health Agencies


Interoperability Need: Case Reporting to Public Health Agencies

Interoperability Need: Case Reporting to Public Health Agencies

Type

Standard/Implementation Specification

Standards Process Maturity

Implementation Maturity

Adoption Level

Federally Required

Cost

Test Tool Availability

1- Implementation Specification

IHE Quality, Research, and Public Health Technical Framework Supplement, Structured Data Capture, Trial Implementation

Balloted Draft

Pilot

 rating 1

No

Free

No

1-Implementation Specification

IHE IT Infrastructure Technical Framework, Volume 1 (ITI TF-1): Integration Profiles, Section 17: Retrieve Form for Data Capture (RFD)

Final

Production

 rating 3

No

Free

Yes

2-Standard

 

HL7 electronic Initial Case Report HL7 C-CDA STU:  HL7 Version 3 Clinical Document Architecture (CDA), Release 2 format.

Balloted Draft

Pilot

 rating 1

No

Free

No

2-Standard

Fast Healthcare Interoperability Resources (FHIR), DSTU 2

Balloted Draft

Pilot

 rating 1

No

Free

No

2- Emerging Implementation Specification

HL7 FHIR DSTU 2, Structured Data Capture (SDC) Implementation Guide

Balloted Draft

Pilot

 rating 1

No

Free

No

2 – Emerging Standard

HL7 FHIR STU 3

In Development

Pilot

N/A

No

Free

No

Limitations, Dependencies, and Preconditions for Consideration:

Applicable Security Patterns for Consideration:

  • 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.
Matthew Greene
Department of Veterans Affairs

For FHIR resource the guidance should identify the specific resource and their level of maturity or status. Some resources will become “normative” in FHIR before other resources. For successful US implementation, we need references to US-localized FHIR profiles organized by use case (i.e. implementation guide).