The Onboarding team will work with your technical teams to ensure a timely and smooth integration.
Once the scope of integration has been determined, a project timeline will be agreed upon between both parties. We typically aim for 8-10 weeks once technical resources have been assigned.
Below is a high level overview of the steps required to integrate with the Vital platform using direct HL7v2 interfaces.
Confirm scope and availability of data
The Vital platform requires several data feeds for optimal functionality (see the HL7v2 Overview for the full list of required interfaces).
Outside of availability, timeliness is also a key factor in the platform's performance, messages should be pushed in real time if possible, otherwise batched every 5-15 minutes if required.
Establish SFTP connectivity
We will need an SSH key in order to create a user; more information can be found in the SFTP article.
Connectivity is confirmed via receipt of a test file.
Build out the required interfaces
This is a joint effort where both sides build out their configuration, ensuring that the data meets the specifications provided in the HL7v2 Overview.
Depending on resource availability, this typically takes 2-3 weeks.
Testing and validation
This involves running through some real-time scenarios commonly experienced in the emergency department. The goal of this is to ensure that all data elements are crossing as and when required.
This typically takes two 2-hour sessions and is a team effort, as we will require both laboratory and imaging orders to be placed and resulted.
Change control and production deployment
Once testing has been completed to everyone's satisfaction and required documentation needs have been met, the build should be submitted to change control and then moved to production.
Internal validation and configuration
Once production data is received, Vital will validate the patient experience and ensure that all data elements reviewed during testing are present.
This typically takes 2-3 weeks; this allows for any adjustments as well as providing our machine learning models with sufficient data ahead of launch.
User Acceptance Testing (UAT)
Prior to Go-Live, we will schedule a call with relevant clinical folks to demonstrate the experience for patients in a production environment using your test domain (see the User Acceptance Testing guide for more information).
Any tweaks to the configuration will be made based on feedback; this will be limited to how patients progress through the application and is not designed to be an open feedback session on the application itself.
Go-Live!
Once internal configuration has been completed, we are now ready to launch technically.
The operational go-live date is largely dependent on the technical piece but is typically 12-13 weeks from kick-off.
For the detailed field-level specifications for each required HL7v2 interface (ADT, Clinical Flowsheets, Clinical Notes, Diagnostic Orders, Diagnostic Results) and data element best practices, see the HL7v2 Overview reference article.