Interoperable Digital Identity and Patient Matching
2.0.0-draft - STU 2.0.0-draft United States of America flag

Interoperable Digital Identity and Patient Matching, published by HL7 International / Patient Administration. This guide is not an authorized publication; it is the continuous build for version 2.0.0-draft built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-identity-matching-ig/ and changes regularly. 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.

Additional constraints for $match

This operation is used by an entity to submit one or multiple GFEs as a Bundle containing the GFE(s) and other referenced resources for processing. The only input parameter is the single Bundle resource with one or multiple GFE(s) - each of which is based on the Claim resource (along with other referenced resources). The only output is a url for subsequent polling per async pattern. If after polling the response is complete, then the result will either be a single Bundle with the AEOB - which is based on the ExplanationOfBenefit resource, (and other referenced resources) or an OperationOutcome resource indicating the AEOB will be sent directly to the patient and not to the provider.

Structures: Resource Profiles

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

IDI Match Bundle

Organization resources SHALL be included.
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.

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