Orange County NC Website
34 <br />4. The next steps depend on the type of data connection your organization will have to NC HealthConnex. <br />a. For a Virtual Private Network (VPN) connection: <br />i. Your organization must complete a VPN connection document. <br />ii. SAS and your technical resources will build a VPN tunnel to your EHR and will <br />coordinate testing with your organization. <br />iii. Test Data will be sent to the Test/stage environment. Any issues will be documented <br />and resolved. <br />iv. Prior to sending data to the production environment, you will be required to provide <br />User Acceptance Approval. <br />v. Data feeds will be promoted to the production environment when all Parties are <br />mutually satisfied with the interface build. Your data will be validated by SAS in <br />collaboration with your technical resource staff and any issues will be documented and <br />resolved. <br />vi. NC HIEA will notify your organization that you have been successfully connected to <br />NC HealthConnex and your Participant Account Administrator will be provided user <br />credentials for the NC HealthConnex Clinical Portal. Training and education materials <br />will be made available to your organization as well. <br />b. For a Batch Secure File Transport Protocol (SFTP) connection: <br />i. Your organization will be assigned to a SAS data connector vendor, who will work with <br />your organization and/or EHR Vendor to build connection to NC HealthConnex. This <br />will require installing software on your EHR system. <br />ii. SAS will implement a daily secure batch transfer of data. <br />iii. The data connector vendor will test file transfers from your EHR to NC HealthConnex. <br />iv. Data will be sent to the Test/stage environment. Any issues will be troubleshooted. <br />v. Prior to sending data to the production environment, you will be required to provide <br />User Acceptance Approval. <br />vi. Data will be sent to the production environment when all Parties are mutually satisfied <br />with the interface build. Your data will be validated by SAS in collaboration with your <br />technical resource staff.. Any issues will be troubleshooted. <br />vii. NC HIEA will notify your organization that you have been successfully connected to <br />NC HealthConnex and your Participant Account Administrator will be provided user <br />credentials for the Clinical Portal, if needed. Training and education materials will be <br />made available to your organization as well. <br />c. For connections built through hubs or interfaces to the NC HealthConnex environment by your <br />EHR vendor, the Onboarding process will depend on your EHR vendor’s system and <br />capabilities, along with any previous work completed by NC HIEA and SAS with your EHR <br />vendor. <br />d. Similarly, if your organization will have HIE Data integrated into your EHR Product, you may <br />not require credentials to access the NC HealthConnex Clinical Portal. Further steps will need <br />to be taken to build and test a bidirectional data connection to your EHR Product. You and your <br />EHR vendor must collaborate with SAS to accomplish integration of HIE Data into your EHR <br />Product. This will require your organization to sign off after the integration is tested prior to <br />production data flowing to your EHR Product. <br />5. Once your connection is established and you have access to NC HealthConnex, any technical issues <br />your Authorized Users encounter should be directed to the SAS Help Desk at HIESupport@SAS.com. <br />Please also consult the Technical Support information provided in Attachment 10. <br />DocuSign Envelope ID: 47B4445A-C7CA-4D2E-9075-2AFD82F82DEC