First, we'll ensure we have the appropriate resources and paperwork (contracts, BAAs, security reviews, etc.) in place to prevent any future delays during the integration process.
This meeting will be used to align on scope (connectivity methods and interfaces required), workflow (how the integration aids end users), and any EHR-specific builds that might be needed. The kickoff meeting also provides an opportunity for the healthcare organization to share vital details for Redox to finalize EHR connectivity and configurations. This often includes specifications or example "messages" (data shared between our system and your EHR). A critical milestone in this phase is to set potential go-live dates. By the end of this call, all necessary details should be shared and follow-up tasks will be identified for efficient progress.
Based on kickoff discussions, Redox and the healthcare organization will set up VPNs or other connection methods. Secure and valid connectivity will be tested in a non-production environment. While production environment connectivity can occur now, it often gets scheduled closer to the go-live event. The goal is to ensure seamless and secure connection before proceeding.
Redox translates specified data between the healthcare organization and Contrast using industry standard, secure application program interfaces (API). This process is two-fold: convert healthcare organization messages to the Redox API and alter the Redox API to the healthcare organization's expected format. This phase often runs in parallel with Phase 2 - Kickoff.
5. Testing & Training
This phase includes functional testing, where Redox and the healthcare organization ensure correct message transformation. It's not a workflow test but ensures technical soundness. The goal is successful message exchange without errors. Application or end-to-end testing tests the integrated workflow using test scripts created by Contrast and Redox, with full oversight as desired by the healthcare organization. Key areas of testing include data elements exchange, workflow triggers for message exchange, and data visibility and timeliness in applications. Redox's involvement is minimal in this phase unless issues arise. End-user testing is optional but encouraged, as it helps end users familiarize themselves with the Contrast platform and builds confidence ahead of go-live.
Pre-go-live involves an administrative step, or "change control", which approves the shift from non-production to production. Preparations also include migrating any customizations or changes made for the healthcare organization. There may be a “soft” go-live to test message volumes and detect missed errors. On the go-live date, all systems are live, end users are informed, and actual patient data flows commence. Contrast also provides production application support mechanisms, including relevant user engagement and error queue monitoring. To summarize, preparation and continuous communication are key!