Demand for healthcare interfaces is rising, and there is a rapid pace in which healthcare entities are working to connect various internal applications and external resources.

Without the right data integrity model, the confidence in the deployed interfaces will be low, and the support costs will be high. Clinical data not received properly, or received in an untimely manner, will quickly erode the healthcare professionals’ acceptance of any previously implemented applications and raise concerns regarding the quality of the information.

There are two perspectives for ensuring a robust data integrity model – interfacing testing and interface monitoring. Interface Testing is the practice of ensuring that the interfaces being developed are of the highest quality prior to deployment. Interface Monitoring is the practice of ensuring that the interfaces continue to operate with a high degree of integrity after deployment.

clinical data integrity model

Depending on the quadrant that a healthcare institution may be in, different characteristics can be defined to the data integrity state. Ideally, an institution will want to be in the top right quadrant – High Performance – which means an equally proactive discipline has been established for both Interface Testing and Interface Monitoring.

For more details on the characteristics of the qualities listed in the diagram, see this Corepoint Health white paper:
Interfacing Insights: What is Your Data Integrity Model?

Tags:
 Print Friendly