Developing the Interface Now that you’ve scoped your interface/integration needs (covered in Part 1), the next step is to develop the interface based on that
3 Considerations for Integrating Your Application in a Healthcare Provider Setting As the technical lead in a healthcare startup, you’ve been focused on building an
Our readers have been asking, and now it’s here: the complete HL7® Survival Guide, now available as a single PDF download. Download your copy now.
Resources For vendor performance rankings, see the KLAS Research website. For a current view of the HL7® interface market within healthcare, see the 2018 HL7®
Anonymization This is a type of de-identification where all sensitive data is removed. More details and a definition of anonymization are available in a previous
Now we’re coming full circle. Throughout Chapters 6 through 10, we talked about creating interfacing artifacts, assets, and documentation: profiles, gap analyses, test plans, test
In the last chapter, we explained what to aim for in test messages and message samples. Next you need to map out your processes and
In the previous chapter, we covered what you need to know when testing your interface. While the right test tool is helpful, you need to
In the last two chapters, we covered some of the requirements-related artifacts you need. Now it’s time for testing, which you conduct at different phases
This chapter helps you set up a crucial HL7® requirements document: the gap analysis. Once you have profiles for your source and destination systems, you