Interoperable Digital Identity and Patient Matching
2.0.0-ballot - STU2 Ballot United States of America flag

This page is part of the Interoperable Digital Identity and Patient Matching (v2.0.0-ballot: STU2 Ballot 1) based on FHIR (HL7® FHIR® Standard) R4. The current version which supersedes this version is 1.0.0. For a full list of available versions, see the Directory of published versions

Artifacts Summary

Contents:

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Behavior: Operation Definitions

These are custom operations that can be supported by and/or invoked by systems conforming to this implementation guide.

IDI Match Operation

This extension of the $match operation is further constrained to meet the additional requirements found in this IG. One of the IDI Patient profiles outline in this guide (IDI-Patient, IDI-Patient-L0, IDI-Patient-L1) SHALL be used as the input for the match request. An IDI-Match-Bundle will be returned to the requesting entity. This Bundle will contain the full URLs of the sourced information, an Organization resource, and any matched Patient resources.

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

FAST Identity UDAP Person

Profile on Person for use with the Interoperable Digital Identity and Patient Matching IG
IDI Match Bundle

Bundle requirements for responders of a $IDI-match request.
IDI Match Input Parameters

The Parameters profile used to define the inputs of the $IDI-match operation using an IDI-Patient profile for submission.
IDI Match Output Parameters

The Parameters profile used to define the outputs of the $IDI-match operation.
IDI Patient

(Base Level) The goal of this profile is to describe a data-minimized version of Patient used to convey information about the patient for Identity Matching utilizing the $match operation. Only requires that 'some valuable data' be populated within the Patient resource and utilizes no weighting of element values.
IDI Patient L0

(Level 0 weighting) The goal of this profile is to describe a data-minimized version of Patient used to convey information about the patient for Identity Matching utilizing the $match operation, and prescribe a minimum set of data elements which meet a combined 'weighted level' of at least 9
IDI Patient L1

(Level 1 weighting) The goal of this profile is to describe a data-minimized version of Patient used to convey information about the patient for Identity Matching utilizing the $match operation, and prescribe a minimum set of data elements which meet a combined 'weighted level' of at least 10 and using attributes that are consistent with an identity that has been verified by the match requestor

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

Identity Identifier Value Set

Codes describing various identifiers to be used in Patient resource for $match.

Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide.

Identity Identifier Code System

Defining codes for describing specialized identifiers to be used in Patient resource for $match.

Terminology: Naming Systems

These define identifier and/or code system identities used by systems conforming to this implementation guide.

Identity-HL7-Identifier

Digital Identifier to assist in patient matching.

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

FASTIDUDAPPerson-Example

Example of Person profile for use with the Interoperable Digital Identity and Patient Matching
IDIMatchInputParameters-Example

Example of IDI-Patient profile for submission as input parameter for $IDI-match operation
IDIMatchOutputParameters-Example

Example of IDI-Patient profile for used to define the outputs of the $IDI-match operation
MATCHOperationResponse

Example of $MATCH operation response with patient and organization
Patient-L0

Example of Patient used as input to $match operation meeting Level 0 information conformance
Patient-L1

Example of Patient used as input to $match operation meeting Level 1 information conformance
Patient1

Example of Patient used as input to $match operation
abc-hospital

Example of Organization used as a hospital for digital identifier
def-idp

Example of Organization used as an identity provider for digital identifier
patient-multi-digital-identifier

Example of Patient where the individual has mulitple Digital Identifiers assigned to them from three different entities: a hospital, a payer, and an IdP.
xyz-payer

Example of Organization used as a payer for digital identifier