Before implementing, you and your connection must:
- Review the workflow in your system and your connection's system. This includes technical steps and any user actions in either system so that you can make informed technical decisions. For your first few implementations, this may be a more in-depth, collaborative process, but if this isn't your first rodeo, you may just need to help your connection understand what it looks like to work with your system.
- Decide what kind of integration to configure for this specific connection. The most common integrations rely on the Redox FHIR® API, Redox Data Model API, an HL7v2 feed, or a proprietary API. You can also learn about alternative integrations. Remember that you must identify which EHR system your connection uses and whether your connection needs to purchase, set up, or reuse any interfaces. Whatever the setup, confirm how exactly your connection plans to send relevant data to your system.
- Discuss data requirements. We recommend providing a list of all the data you want from your connection's system and determine which patient identifier(s) should be used. Then, decide how all the data elements should be mapped between systems. It may also be helpful to refer to Redox message size limits so you know what to plan for data-wise. Also, review our API reference for any data requirements for the FHIR® resources/notifications or Redox data models you expect to use.
- Talk about Redox's role in your integration. Redox's involvement is covered under HIPAA in a subcontractor capacity, whether we're the subcontractor under a covered entity or a Business Associate Agreement (BAA) between you and your connection. If your connection needs more information, they can talk to a Redoxer directly. Also, feel free to send these resources to your connection so they can learn about Redox:
Even with the best-laid plans, implementations may not always go quickly or as expected. We see the average time from kickoff to go-live being about 6 to 10 weeks, but it all depends on how quickly you and your connection can implement, as well as how many data exchange methods you're using and any needed customization.
We wanted to share some common issues we've seen and best practices to help meet timelines.
- Process delays during implementation.
- Competing projects.
- Limited experience or knowledge for Integration analysts.
- Adjusted scope in implementation.
- Needing a new integration feed.
- Integrating with a new EHR system.
- Redox requiring new development.
- Share timelines early and have weekly check-ins.
- Find out if there are any competing projects in the pipeline.
- Establish escalation paths and contacts.
- Check if you can fill roles with your connection's team or if you need support from EHR system team members before kicking off implementation.
- Be prescriptive instead of offering multiple options so you can kick off with a solid scope. If at all possible, avoid scope ambiguity.
- Consider implementing in phases, i.e., go live as you complete development in stages. You can always iterate on an implementation, but start with the minimum to go-live sooner.
- Decide what integration methods and feeds you're using ahead of time; consider using existing feeds or interim options if you have them.
- Set reasonable expectations according to scope and new development work. Allow buffer time for EHR interface development.
- Plan for future projects to ensure any new data elements to remain scalable.
- Clearly define data requirements, then review your workflow and expected data elements with Redox.
- Create your own integration materials like project plans, data requirements and mapping, workflow diagrams with proposed data exchange methods for your connection to review so they can accurately plan for implementation.
- Keep your product/engineering teams from your tech onboarding to Redox engaged throughout your first implementation project. Their involvement is invaluable to ensure a full transition of knowledge from start to finish.