1. HealthIT.gov
  • Print

Interoperability Need: Reporting Syndromic Surveillance to Public Health (Emergency Department, Inpatient, and Urgent Care Settings)


Interoperability Need: Reporting Syndromic Surveillance to Public Health (Emergency Department, Inpatient, and Urgent Care Settings)

Interoperability Need: Reporting Syndromic Surveillance to Public Health (Emergency Department, Inpatient, and Urgent Care Settings)

Type

Standard/Implementation Specification

Standards Process Maturity

Implementation Maturity

Adoption Level

Federally Required

Cost

Test Tool Availability

Standard

HL7 2.5.1

Final

Production

 rating 5

Yes

Free

No

Implementation Specification

PHIN Messaging Guide for Syndromic Surveillance: Emergency Department and Urgent Care Data Release 1.1 and Conformance Clarification for EHR Certification of Electronic Syndromic Surveillance, Addendum to PHIN Messaging Guide for Syndromic Surveillance 

Final

Production

 rating 4

Yes

Free

Yes

Emerging Implementation Specification

PHIN Messaging Guide for Syndromic Surveillance: Emergency Department, Urgent Care, Inpatient and  Ambulatory Care Settings, Release 2.0 and Erratum to the CDC PHIN 2.0 Implementation Guide, August 2015; Erratum to the CDC PHIN 2.0 Messaging Guide, April 2015 Release for Syndromic Surveillance: Emergency Department, Urgent Care, Inpatient and Ambulatory Care Settings

Final

Pilot

 rating 1

Yes

Free

No

Limiations, 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 syndromic surveillance data as there may be jurisdictional variation or requirements.
  • An Erratum to the CDC PHIN 2.0 Implementation Guide was issued in August, 2015. Implementers should refer to this guide for additional information and conformance guidance.
  • See HL7 V2 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.
Amy Ising
International Society for Disease Surveillance

Please note that there is a NIST tool available at http://hl7v2-ss-r2-testing.nist.gov/ss-r2/#/home for the
HL7 V2.5.1 PHIN Messaging Guide Release 2.0 and associated Erratum for Syndromic Surveillance.