Master Patient Index (MPI)
See the following -
Building An Effective ACO: Longitudinal Records Enable Collaboration
Once an accountable care organization (ACO) or other collaborative care entity has laid the foundation for a robust health data exchange by ensuring the electronic capture of complete clinical and financial information at the individual provider level, the next step is to build the core of the structure – the longitudinal patient record. Read More »
- Login to post comments
CONNECT releases open-source HIE software
For national and local health information exchanges (HIEs) running on the CONNECT platform, there’s a new version 3.2.1. CONNECT that uses Nationwide Health Information Network (NHIN) standards and governance to make sure that HIEs are compatible with other exchanges being established across the country. Read More »
- Login to post comments
Defining An Open Platform for Health IT
It is widely agreed that the future of digital health lies in an “Open Platform”. However, it’s not clear as to exactly what an Open Platform is or how we get there. This blog aims to answer the first question and to provide some guidance on the second. While any given instance of an Open Platform will be a specific implementation of a set of software components owned and operated by a particular organisation (this might be a health and social care organisation or a third party, operating the platform on behalf of a local health and care community), it is most usefully defined by a set of principles rather than the specific details of a particular implementation.
- Login to post comments
Plug and Play Healthcare: Open Middleware and the Emergence of a Functional Interoperability Framework
“A middleware architecture has been shown to be the best technological solution for addressing the problem of EHR interoperability. The middleware platform facilitates the transparent, yet secure, access of patient health data, directly from the various databases where it is stored. A server-based middleware framework supporting access to the various patient health data stores allows for a scalable, unified and standardized platform for applications to be developed upon. The middleware architectural design has been successfully used to link data from multiple databases, irrespective to the database platform or where the database is located,” says Voltz. Read More »
- Login to post comments
Report on ONC’s Working Session on Patient Identity and Matching
On Monday, August 31, I attended the final Working Session on Patient Identity and Matching. This virtual event was hosted by the Office of the National Coordinator for Health IT (ONC). This Working Session was a followup to an earlier session back in June 2020. The event last week had over 300 attendees and covered a wide range of topics and technologies related to patient identity and matching. These ONC Working Sessions are being driven by requirements that are part of the 21st Century Cures Act as well as a Congressional request from December 2019 to continue to "...evaluate the effectiveness of current [patient identity and matching] methods and recommend actions that increase the likelihood of an accurate match of patients to their health care data." Much of the focus of this study has been on whether a national patient identifier should be implemented in the US.
- Login to post comments
Successful Public Health IT Project Collaboration
- Login to post comments
Why Making the Case for Interoperability Standards Is Needed
It's buzzy. It's the fly in the ointment for many and vendors swear it's seriously. just. about. to. gain. traction. Interoperability. Thinking about the topic is daunting itself but for those on the frontlines of care delivery and for patients, its increasingly becoming necessary as the healthcare industry enters into a more networked era. When we last checked in on interoperability, the industry was touting the massive adoption of EHRs...
- Login to post comments