Interoperable Digital Identity and Patient Matching
3.0.0-current - STU 3 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 3.0.0-current 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

Extension: vLEI

Official URL: http://hl7.org/fhir/us/identity-matching/StructureDefinition/VLEI Version: 3.0.0-current
Standards status: Trial-use Maturity Level: 2 Computable Name: VLEI
Other Identifiers: OID:2.16.840.1.113883.4.642.40.81.42.11

An extension to hold the verified LEI (vLEI) indicating that the LEI has been verified and is valid. Note that the vLEI is not further decomposed into the Attachment elements, as pulling these values outside of the vLEI leaves them unprotected. Thus any access to the vLEI elements should go through the proper vLEI validation process and use the values in the then validated vLEI.

Context of Use

    This extension may be used on the following element(s)

Usage info

Usages:

You can also check for usages in the FHIR IG Statistics

Formal Views of Extension Content

Description Differentials, Snapshots, and other representations.

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Extension 0..* Extension vLEI
... extension 0..0 Extension
... url 1..1 uri "http://hl7.org/fhir/us/identity-matching/StructureDefinition/VLEI"
... value[x] S 1..1 Attachment Value of extension
.... contentType S 1..1 code Mime type of the content, with charset etc.
Required Pattern: application/json
.... language 0..0 Human language of the content (BCP-47)
.... data S 1..1 base64Binary Data inline, base64ed
.... url S 0..1 url Uri where the data can be found
.... size 0..0 Number of bytes of content (if url provided)
.... hash 0..0 Hash of the data (sha-1, base64ed)
.... title 0..0 Label to display in place of the data
.... creation 0..0 Date attachment was first created

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Extension 0..* Extension vLEI
... id 0..1 string Unique id for inter-element referencing
... extension 0..0 Extension
Slice: Unordered, Open by value:url
... url 1..1 uri "http://hl7.org/fhir/us/identity-matching/StructureDefinition/VLEI"
... value[x] S 1..1 Attachment Value of extension
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
.... contentType SΣ 1..1 code Mime type of the content, with charset etc.
Binding: Mime Types (required): The mime type of an attachment. Any valid mime type is allowed.
Required Pattern: application/json
.... data S 1..1 base64Binary Data inline, base64ed
.... url SΣ 0..1 url Uri where the data can be found
Example General: http://www.acme.com/logo-small.png

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Extension.value[x].contentType Base required MimeType 📍4.0.1 FHIR Std.

Constraints

Id Grade Path(s) Description Expression

Summary

Simple Extension with the type Attachment: An extension to hold the verified LEI (vLEI) indicating that the LEI has been verified and is valid. Note that the vLEI is not further decomposed into the Attachment elements, as pulling these values outside of the vLEI leaves them unprotected. Thus any access to the vLEI elements should go through the proper vLEI validation process and use the values in the then validated vLEI.

Maturity: 2

Differential ViewDifferential View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Extension 0..* Extension vLEI
... extension 0..0 Extension
... url 1..1 uri "http://hl7.org/fhir/us/identity-matching/StructureDefinition/VLEI"
... value[x] S 1..1 Attachment Value of extension
.... contentType S 1..1 code Mime type of the content, with charset etc.
Required Pattern: application/json
.... language 0..0 Human language of the content (BCP-47)
.... data S 1..1 base64Binary Data inline, base64ed
.... url S 0..1 url Uri where the data can be found
.... size 0..0 Number of bytes of content (if url provided)
.... hash 0..0 Hash of the data (sha-1, base64ed)
.... title 0..0 Label to display in place of the data
.... creation 0..0 Date attachment was first created

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Extension 0..* Extension vLEI
... id 0..1 string Unique id for inter-element referencing
... extension 0..0 Extension
Slice: Unordered, Open by value:url
... url 1..1 uri "http://hl7.org/fhir/us/identity-matching/StructureDefinition/VLEI"
... value[x] S 1..1 Attachment Value of extension
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
.... contentType SΣ 1..1 code Mime type of the content, with charset etc.
Binding: Mime Types (required): The mime type of an attachment. Any valid mime type is allowed.
Required Pattern: application/json
.... data S 1..1 base64Binary Data inline, base64ed
.... url SΣ 0..1 url Uri where the data can be found
Example General: http://www.acme.com/logo-small.png

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Extension.value[x].contentType Base required MimeType 📍4.0.1 FHIR Std.

Constraints

Id Grade Path(s) Description Expression

Summary

Simple Extension with the type Attachment: An extension to hold the verified LEI (vLEI) indicating that the LEI has been verified and is valid. Note that the vLEI is not further decomposed into the Attachment elements, as pulling these values outside of the vLEI leaves them unprotected. Thus any access to the vLEI elements should go through the proper vLEI validation process and use the values in the then validated vLEI.

Maturity: 2

 

Other representations of profile: CSV, Excel, Schematron