| PHESS Checklist | Updated on : 06/18/2018 | ||
| Step 1: Register Intent to submit PHESS | |||
| Yes | Date | Comments & Resources | |
| ISDH will only accept providers that are classified as either a Hospital with an ED, an immediate care, or urgent care facility for Meaningful Use Stages 2 & 3. ISDH will not be able to attest other provider types until after January 1, 2019. | ☒ | ||
| Submit your registration via the ISDH Meaningful Use Site for Registration of Intent. | ☒ | REQUIRED FOR STAGE 2 & 3 OF MU. | |
| Receive and retain your notification from ISDH that your registration has been completed and received. | ☒ | ||
| Step 2: Identify PHESS data that are required by Indiana law to be reported to ISDH | |||
| Yes | Date | Comments & Resources | |
| Download a copy of the CDC standard HL7 Version 2.5.1 Implementation Guide: PHIN MESSAGING GUIDE FOR SYNDROMIC SURVEILLANCE: EMERGENCY DEPARTMENT, URGENT CARE AND INPATIENT SETTINGS. | ☒ | PHIN Messaging Guide for Syndromic Surveillance: Emergency Department, Urgent Care, Inpatient and Ambulatory Care Settings, Release 2.0 (April, 2015) | |
| Download
and READ a copy of the Indiana State Department of Health HL7 Version 2.5.1
Syndromic Messaging Guide. This will help to develop a message that will pass ISDH's testing process. |
ISDH PHESS Messaging Document | ||
| Step 3: Participate in initial planning discussion with ISDH | |||
| Yes | Date | Comments & Resources | |
| Contact ISDH to let us know that you are ready to begin testing, or to schedule an initial planning discussion. | ☒ | Send an email to isdhelrss@isdh.in.gov . | |
| Receive and retain your invitation to initiate on-boarding for PHESS/Syndromic Surveillance reporting from ISDH. | ☒ | ||
| Step 4: Develop an HL7 Version 2.5.1 Message for PHESS | |||
| Yes | Date | Comments & Resources | |
| Develop HL7 messages conformant to the ISDH PHESS Messaging Document (from step 2 above). | ☒ | ||
| Test PHESS messages via online
NIST validation tool, resolve issues found, and provide your successful
validation results to ISDH. NOTE: Do not use real personally identifiable information in the online tool. Only use test data. |
☒ | National Institute of Science and Technology (NIST) website | |
| NIST Instructions from ISDH | |||
| Step 5: NIST Reports and secure message transport connectivity | |||
| Yes | Date | Comments & Resources | |
| Please
email NIST PDF reports with 5 or fewer errors for one of each of the
following message types to ISDH: A01/A04 (Register/Admit), A08 (Update), A03 Discharge |
☒ | ||
| ISDH
currently supports SFTP as the transport mechanism for sending PHESS data
directly to ISDH. You may also send your messages via a Health Information Exchange (HIE) or vendor direct to ISDH. Please contact ISDH to request configuration of the SFTP transport mechanism. |
☒ | Send an email to isdhelrss@isdh.IN.gov to setup SFTP account. | |
| Step 6: Send a file via SFTP containing a test message for initial validation | |||
| Yes | Date | Comments & Resources | |
| Transmit a message or messages containing PHESS test cases according to the requirements defined in the ISDH PHESS Messaging Document (from step 2. above). | ☒ | ||
| Receive and retain your confirmation that a successful test message has been received by ISDH. | ☒ | ||
| Step 7: Structure and content validation | |||
| Yes | Date | Comments & Resources | |
| ISDH will perform structure and content validation, and send feedback. | ☒ | ||
| Fix any issues that have been addressed and resend test messages. Continue this process until ISDH has approved the messages to move to production. | ☒ | If your facility is non-responsive, you many not fulfill the Meaningful Use objective for ELR. | |
| Step 8: Schedule production implementation | |||
| Yes | Date | Comments & Resources | |
| Determine when your facility is able to move the data transmissions to production and schedule with ISDH. | ☒ | ||
| Once moved to production, ISDH will verify if we are receiving the messages. | ☒ | ||