HIE Participant Onboarding Resources

Documents & Artifacts

• New World HIE On-Boarding Readiness Questionnaire
• New World HIE ADT Technical Design Document
• New World HIE Sample CCDA Use Case

Lessons Learned

Connectivity

Need a standardized, timely, and proven approach for testing and implementing VPNs and connectivity.

• 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…
• Established timeline for go-live
  • Testing
  • UAT
  • Activation
  • Go-live issue resolution

Preparedness

• Inbound Feeds
  • Version control – ensure interfaces are complete and thorough testing has occured prior to promoting them to production
  • Environment control – it’s important that all environments are the same, so any testing conducting in dev and test environments can be relied upon as sufficient
• Outbound Feeds
  • Understand how they function, where input facility specific logic needs to be input, etc…

Documentation of Standards

• Prefixes and Suffixes
• PV1 Providers and Copy To Providers in OBR NTE Segments
• OBX-3 is a copy of ‘OBR-4’ on RADs
• Naming Conventions

User Acceptance Testing

• Ensure that aesthetic formats and HL7 standards are met
  • OBR-4/OBX-3
  • PV1 Providers in NTE segments
  • Map OBR-4 to OBX-3 on RADs if OBX-3 is of no value
• Follow Test Plans through each message type
  • Event types and message order
  • Cancellations and corrections
  • Microbiology messages and pathology messages
  • Sensitive Lab testing
  • Look for invalid characters
• Create a schedule for validation in Stage, sign-off, validation in Prod, sign-off
  • Standardized process for HIE Validation
  • Standardized process for Participant UAT Validation
  • Standardized process for migration through environments