This page is part of the IHE Patient Master Identity Registry (PMIR) (v1.5.0: Trial Implementation) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions

1:49 Patient Master Identity Registry (PMIR) Profile

Official URL: https://profiles.ihe.net/ITI/PMIR/ImplementationGuide/ihe.iti.pmir				Version: 1.5.0
Active as of 2022-08-09				Computable Name: IHE_ITI_PMIR

The Patient Master Identity Registry (PMIR) Profile supports the creating, updating and deprecating of patient master identity information about a subject of care, as well as subscribing to changes to the patient master identity, using the HL7 FHIR standard resources and RESTful transactions. In PMIR, “patient identity” information includes all information found in the FHIR Patient Resource such as identifier, name, phone, gender, birth date, address, marital status, photo, others to contact, preference for language, general practitioner, and links to other instances of identities. The “patient master identity” is the dominant patient identity managed centrally among many participating organizations (a.k.a., “Golden Patient Identity”).

Beyond the basic create, retrieve, update, and delete transaction set, this profile addresses important patient safety issues related to cases where there are two or more patient master identities that have been established for the same person, thus it is not clear which identity is the “true” one. There is also a risk that health data (possibly conflicting) may be associated with each identity – and these disparate data, together, may need to be reconciled before a fully and accurate “health picture” can be developed for this person. These situations represent patient safety risks. This profile addresses how these multiple patient master identities can be merged into a single patient master identity, and how this merge flows down to data custodians so that they take appropriate actions. It is outside the scope of this profile to define how references to the deprecated patient master identity from other data should be handled.

This profile is intended for FHIR-only configurations without other underlying standards for patient master identity management. The FHIR message pattern was chosen because it fits well into the subscription notification model.

Organization of This Guide

This guide is organized into four main sections:

1. Volume 1: Profiles
   1. PMIR Introduction
   2. PMIR Actors, Transactions, and Content Modules
   3. PMIR Actor Options
   4. PMIR Required Actor Groupings
   5. PMIR Overview
   6. PMIR Security Considerations
   7. PMIR Cross Profile Considerations
2. Volume 2: Transaction Detail
   1. Mobile Patient Identity Feed [ITI-93]
   2. Subscribe to Patient Updates [ITI-94]

3. Test Plan

4. Changes to other Profiles

Click on any of the links above, navigate the contents using the table of contents, or if you are looking for a specific artifact, check out the artifacts.

Conformance Expectations

IHE uses the normative words: Shall, Should, and May according to standards conventions.

Must Support

The use of mustSupport in StructureDefinition profiles equivalent to the IHE use of R2 as defined in Appendix Z.

mustSupport of true - only has a meaning on items that are minimal cardinality of zero (0), and applies only to the source actor populating the data. The source actor shall populate the elements marked with MustSupport if the concept is supported by the actor, a value exists, and security and consent rules permit. The consuming actors should handle these elements being populated or being absent/empty. Note that sometimes mustSupport will appear on elements with a minimal cardinality greater than zero (0), this is due to inheritance from a less constrained profile.

Download

You can also download:

• this entire guide,
• the definition resources in json, xml, ttl, or csv format, or
• the example resources in json, xml or ttl format.

The source code for this Implementation Guide can be found on IHE GitHub.