Interoperable Digital Identity and Patient Matching
1.0.0-ballot - STU Ballot 1 US

This page is part of the Interoperable Digital Identity and Patient Matching (v1.0.0-ballot: STU 1 Ballot 1) based on FHIR R4. . 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.

Structures: Resource Profiles

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

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 10
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 20

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.

Example: Example Instances

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

Patient1

Example of Patient used as input to $match operation
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