HIE Participant Onboarding Resources
Revision as of 13:56, 9 September 2016 by Justin.Campbell (talk | contribs) (Created page with "=Lessons Learned= ==Connectivity== Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.<br> Checklist:<br> *What type of connec...")
Lessons Learned
Connectivity
Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.
Checklist:
- What type of connection will the participant be using?
- VPNs should be completed prior to engaging participants for kick-off calls, so progress can be made without losing communication with participant
- How many VPNs can be completed concurrently?
- How many dedicated connectivity resources will the HIE have dedicated?
- Which participants are ready to engage at what time?
- Does HIE have a schedule in terms of building these VPN connections?
- VPN connectivity to all HIE environments: Test, Stage, Prod
Kick Off Meetings with Net New Participants
The following should be complete prior to kick off call if possible:
- Will participants be receiving information from HIE (outbound to participant)?
- If so, what specs do they need to receive for each message type they plan to receive?
- What types of interfaces will the participant be connecting to HIE (inbound from participant)?
- System code for facility added to system and portal
- If participant is sending ORUs:
- Are all results LOINC Coded?
- Understanding how OBR-4/OBX-3 is sent
- Ensure corrections, cancellations work as participant expects, etc…
- Proper handling of sensitive lab information/do they send it?
- If sending radiology, will they be participating in an Image Exchange?
- Interface Analyst Contact Information
- Phone/email
- UAT Contacts (Validators)
- Phone/email
- Test plan for UAT from participant?
- If not, we need one
- ADT – event type flow, testing all event types
- ORU – testing cancellations, corrections (both OBR and OBX), testing microbiology results, testing pathology results
- MDM – testing cancellations, corrections, etc…
- If not, we need one
- Established timeline for go-live
- Testing
- UAT
- Activation
- Go-live issue resolution