De-Duplicating the received duplicate data

Everything has failed in duplicate data. In health care, there is a new cry from doctors because of their failure to see duplicate data. The positive thing is you get the data now. Therefore, we must succeed in interoperability with all efforts to exchange patient health information and access to its data.

We quickly set quality standards in our seat because we can not avoid this double problem … well and not. Each standard we have established contains specific mechanisms that prevent duplication. However, when you use these standards, engagements are created. It can be abbreviated in the development of the program. Joining may be in the network implementation. Shortcuts can be in the network. It can be abbreviated when creating data. It can be abbreviated when exporting data. It can be abbreviated when the data is “used” but abbreviations when the standard is not used as intended.

Are these links bad? Not required Often a shortcut is selected for the solution to work quickly. If the abbreviations are not used, we will not be today. Abbreviations are good in short terms. Abbreviations are only bad if they are not corrected as soon as they are identified as a problem. Some keyboard shortcuts are not a problem.

Common solutions for double data
In today’s standards (XDS, XCA, CDA, Direct), let me know what can be used to prevent data duplication:

Patient Identity: The protocols create a virtual identity of many identities given to patients of many different organizations. (XCPD, PIX, PDQ, etc.)
Home Community ID: a unique identifier for a community of organizations (organizations)
Patient Identification Authority (AA): specifically refers to the body that provides patient IDs. Usually one for every health organization, although it can be assigned to a higher level.
Unique Document ID: The document identified specifically, regardless of how it was received (even if it was received through the Direct or Patient portal)
Unique ID for retrieval documents: The input of documents consists of metadata in a document, including unique ID document. An entry document contains a unique identifier.
Article ID: It may not be used today, but is supported by the standard. Basic core for FHIR
Source: This is unlikely to be available today, but it is uniquely identifying the source
Prepare these points
This is a complex problem and many layers are used to solve different parts of the complex problem. Each layer is related to a certain part of the complexity.
Discover the identity of the virtual patient.
Protocols such as IHE PIX, PDQ and XCPD are used to identify different identities known to the patient. This is true even if the government needs a national identifier.
Double network routes
The most common reason for data duplication is that there are many paths in the same data repository (documents). Like HealtheWay, CommonWell or CareQuality. Use only one of these methods, and do not have many routes. Use some, and you can do it. The reason for using more than one factor is the fact that each network has a subset of comprehensive service providers. Duality is that some share more than one network … like you … So if no one is involved in multiple networks, there are no duplicate routes.

Heatmap for the CareQuality network

Finally, you may find that you have two or three contacts for the same health organization. You can disable the selected endpoints only on certain networks. Choose to talk only to a partner in a network. I would like to say that the prevention process will be at the beginning of small technological and effective. But while the network is expanding and expanding, we need a way to identify a new recurring path.

I suggest that multiple routes can be useful to address the major calamities that leave a network or route.

Duplicate routes will be identified and if they are noticed they can be automatically intercepted.

Leave a Reply

Your email address will not be published. Required fields are marked *