HL7 Case Notification Implementation Public Health Agency (PHA) Readiness Checklist
| | Readiness | Description |
|---|---|---|
| ☐ | Technical Infrastructure | The PHA’s infrastructure (i.e., the hardware, software, network resources, and related systems) should have the minimum requirements to create, generate, validate, and transport HL7 case notification messages. |
| ☐ | Test Environment | The PHA’s test environment should mimic the workflows of the production environment, and the relationship of the systems in the test environment should mirror those of the production environment. |
| ☐ | Transport | The PHIN Messaging System (PHINMS) (https://www.cdc.gov/phin/tools/PHINms/) is the preferred method of transport for HL7 case notification messages. PHAs sending HL7 messages though PHINMS will need to establish PHINMS connectivity and obtain the necessary certificates. PHAs that either cannot establish PHINMS connectivity or would like to identify alternative transport options can discuss further with CDC. |
| ☐ | Expertise/Resources | The table below summarizes specific roles that are required at the PHA to implement HL7 messaging for case notifications. The level of effort for experts in each role will vary by PHA and likely by condition. In general, PHA program SMEs are primarily involved early in the process to reconcile condition-specific MMG fields with surveillance system data, while the PHA’s IT implementer is involved later to create and validate the HL7 message. |
| Implementation Team Role | Name | Phone | |
|---|---|---|---|
| Project Lead/Champion | |||
| Lead for Integrated Surveillance System | |||
| Person Responsible for Gap Analysis | |||
| Person Responsible for Creating Electronic Messages | |||
| Person Responsible for Configuring Message Transport | |||
| Person Responsible for Data Administration of PHA Surveillance System for Conditions Covered by MMG |