 HL7 PA, R2-2010 HL7 Version 3 Standard: Patient Administration, DSTU Release 2 Update February 2010 Update to DSTU Release 2 |
Content Last Edited: 2011-06-17T13:44:56
3.2 Storyboards
3.3 Application Roles
3.4 Trigger Events
3.5 Refined Message Information Models
3.6 Hierarchical Message Descriptions
3.7 Interactions
The Identify Document topic focuses narrowly on information exchanges with person identification document registries. The focus is on verifying the validity of a document such as a passport or driver's license and not on authenticating the identity of the person presenting the document.
This DSTU update contains no updates to the R2-2007 content.
The Patient Administration work group is not aware of any implementers of this topic in the DSTU and is considering withdrawing it from the standard before normative ballot.
|
||||||
|
For details on the interpretation of this section, see the storyboard discussion in the Version 3 Guide.
| Document Validity Verification Request |  PRPA_IN900101UV02 |
| Document Validity Verification Response | PRPA_IN900102UV02 |
| Document Validity Verification Rejected | PRPA_IN900103UV02 |
A person shows up at the Good Health Hospital and uses his Dutch Passport (with number NP835243239) to identify himself. As part of the process of verifying if the person (as a biological entity) is Kees ter Beek, the clerk in the hospital sends a Document Validity Verification Request to a governmental identification-document-registry.
The request is rejected by the registry because the clerk does not have the authorization to request a verification. The registry responds with a Document Validity Verification Rejected and identifies the authorization issue as a reason for the reject. The reject interaction does not make any statement about the validity of the document.
|
||||||||
|
For details on the interpretation of this section, see the discussion of application roles and their relationships in the Version 3 Guide.
This application role represents applications that need to determine whether an identification document is valid.
This application role represents the responsibility of a person identification document registry to respond to document validity
verification requests. The application must either accept or reject the request. When it accepts the verification request
it must return an indication as to whether the identification document is valid or not.
|
||||||||||
|
For details on the interpretation of this section, see the discussion of trigger events in the Version 3 Guide.
| Type: | User request |
A source system sends a request to a document registry to verify the validity of an identification document.
| Type: | Interaction based |
| Type: | Interaction based |
|
||||||||||
|
For details on the interpretation of this section, see the description of RMIMs in the Version 3 Guide.
| Parent: | Patient Administration (PRPA_DM000000UV) |
Overview
The Document Validity Verification Request R-MIM defines the payload for a request message sent to an Identification Document Registry. The R-MIM contains the details of the requested document validity verification activity as well as details of the identification document that is the subject of the requested verification act.
Walk-through
VerficationRequest: An act identifying a request for verification
- id: Identifier for the verification request
- code: Code identifying the type of verification
- effectiveTime: Time of the requested verification event
- priorityCode: A code (e.g., for routine, emergency), specifying the urgency under which the verification act is requested to happen
- reasonCode: A code specifying the motivation, cause or rationale for the verification request
- author participation: The person, organization or device that requested the verification, and the organization they represent, are identified via this participation.
- subject Act Relationship: This relationship associates a verification request with its subject: the identification document
R_Responsible CMET: A CMET identifying the party that requested the document validity verification
IdentityDocument: An identification document that is the subject of the verification process
- id: Identifier of the identification document
- code: Code identifying the type of identification document (e.g. passport, drivers license)
- subject Participation: The person whose details are shown on the identification document
| Document Validity Verification Request | PRPA_HD900101UV02 |
| Parent: | Patient Administration (PRPA_DM000000UV) |
Overview
This Document Validity Verification Response R-MIM contains the details of the verification of the validity of an identification document and the result of the validity verification (document is valid or not valid).
Walk-through
Verification: An act that identifies the verification event. The verification process and results are described through classes associated with this Act
- id: identifier for the verification event
- code: code identifying the type of verification. Codes are taken from the ActVerificationTypeCode domain
- effectiveTime: time of the verification event
- value: the actual outcome of the verification process e.g. 'verified', 'not verified'
- inFullfillmentOf Act Relationship: This relationship associates a verification event with one VerificationRequest
- PrimaryPerformer Participation: The person, organization or device that actually performed the verification, and the organization they represent, are identified via this participation
- subject Act Relationship: This relationship associates a verification event with its subject: the identification document.
VerificationRequest: An act identifying a request for verification. Apart from an event identifier the particulars of the request are not supported in this model
- id: identifier for the verification request
R_AssignedEntity CMET: A CMET identifying the party which has performed the document validity verification (e.g. the issuing authority, or a party acting on behalf of that authority)
IdentityDocument: An act representing the identification document that is the subject of the verification process
- id: identifier for the identification document
- code: code identifying the type of identification document (e.g. passport, drivers license)
- subject Participation: The person whose details are shown on the identification document
| Document Validity Verification Response | PRPA_HD900102UV02 |
| Parent: | Patient Administration (PRPA_DM000000UV) |
Overview
The Document Validity Verification Request Rejected R-MIM only identifies the document validity request that is being rejected. The reason(s) for the rejection are found in the wrappers.
Walk-through
ValidityVerification: An act identifying a request for verification
- id: identifier for the verification request (mandatory)
| Document Validity Verification Request Rejected | PRPA_HD900103UV02 |
|
||||||||||
|
For details on the interpretation of this section, see the description of HMDs in the Version 3 Guide.
The Document Validity Verification Request payload message contains the details of a user request sent to an identification document registry to verify the validity of an identity device (e.g., document, chipcard).
| R_ResponsibleIdentified/informational | COCT_MT040008UV |
| Document Validity Verification Request | PRPA_MT900101UV02 | |
| R_AssignedEntityIdentified/informational | COCT_MT090008UV |
| Document Validity Verification Response | PRPA_MT900102UV02 | |
| Document Validity Verification Request Rejected | PRPA_MT900103UV02 | |
|
||||||||||
|
For details on the interpretation of this section, see the definition of Interactions in the Version 3 Guide.
A user initiates a request to an identification document registry to verify the validity of an identification document.
| Trigger Event | Document Validity Verification Request | PRPA_TE900101UV02 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Document Validity Verification Request | PRPA_MT900101UV02 |
| Reason | Trigger Event | Interaction |
| If a Verification Request Fulfiller application role accepts a request to verify the validity of a document it must respond back with the identifier of the request and the result of the verification | PRPA_TE900102UV02 | PRPA_IN900102UV02 |
| If a Verification Request Fulfiller application role rejects a request to verify the validity of a document then it must respond back with the identifier of the request and the reason(s) it was rejected | PRPA_TE900103UV02 | PRPA_IN900103UV02 |
| Sender | Document Validity Verification Placer | PRPA_AR900101UV02 |
| Receiver | Document Validity Verification Fulfiller | PRPA_AR900102UV02 |
An identification document registry accepts a request to verify the validity of an identification document. The registry carries out the the verification and returns the verification results to the requesting system.
| Trigger Event | Document Validity Verification Response | PRPA_TE900102UV02 |
| Transmission Wrapper | Application Level Acknowledgement | MCCI_MT000300UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Document Validity Verification Response | PRPA_MT900102UV02 |
| Sender | Document Validity Verification Fulfiller | PRPA_AR900102UV02 |
| Receiver | Document Validity Verification Placer | PRPA_AR900101UV02 |
An identification document registry encounters errors while processing a request to verify the validity of an identification document and rejects the verification request.
| Trigger Event | Document Validity Verification Rejected | PRPA_TE900103UV02 |
| Transmission Wrapper | Application Level Acknowledgement | MCCI_MT000300UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Document Validity Verification Request Rejected | PRPA_MT900103UV02 |
| Sender | Document Validity Verification Fulfiller | PRPA_AR900102UV02 |
| Receiver | Document Validity Verification Placer | PRPA_AR900101UV02 |
| Return to top of page |