The QRI segment is used to indicate the weight match for a returned record (where the responding system employs a numeric algorithm) and/or the match reason code (where the responding system uses rules or other match options).
Examples of the use of this segment appear in Chapter 3, "Patient Administration," section 3.3.57, "Find Candidates and Response."
HL7 Attribute Table - QRI - Query Response Instance
| Base Framework | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Seq# | Data Element | Description | Flags | Implement | Cardinality | Length | C.LEN | Vocabulary | Data Type | |
 QRI | ||||||||||
  | 1 | 01436 | Candidate Confidence | = Truncation allowed. | MAY | [0..1] | 10 | NM Numeric | ||
| 2 | 01437 | Match Reason Code | MAY | [0..*] | [2..2] | ex.:MatchReason (CD) | CWE Coded with Exceptions | ||
 | 3 | 01438 | Algorithm Descriptor | MAY | [0..1] | ex.:MatchAlgorithms (CD) | CWE Coded with Exceptions | |||
| Seq# | Data Element | Description | Flags | Implement | Cardinality | Length | C.LEN | Vocabulary | Data Type | |
|---|---|---|---|---|---|---|---|---|---|---|
| QRI | ||||||||||
| 1 | 01436 | Candidate Confidence | = Truncation allowed. | MAY | [0..1] | 10 | NM Numeric | ||
| 2 | 01437 | Match Reason Code | MAY | [0..*] | [2..2] | ex.:MatchReason (CD) hl7VS-matchReason (VS) matchReason (CS) | CWE Coded with Exceptions | ||
| 3 | 01438 | Algorithm Descriptor | MAY | [0..1] | ex.:MatchAlgorithms (CD) | CWE Coded with Exceptions | |||
| Base Framework | Base Standard Profile | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Seq# | Data Element | Description | Flags | Implement | Cardinality | Length | C.LEN | Vocabulary | Data Type | Implement | Vocabulary | |
| QRI | ||||||||||||
| 1 | 01436 | Candidate Confidence | = Truncation allowed. | MAY | [0..1] | 10 | NM Numeric | MAY | |||
| 2 | 01437 | Match Reason Code | MAY | [0..*] | [2..2] | ex.:MatchReason (CD) | CWE Coded with Exceptions | MAY | hl7VS-matchReason (VS) matchReason (CS) | ||
| 3 | 01438 | Algorithm Descriptor | MAY | [0..1] | ex.:MatchAlgorithms (CD) | CWE Coded with Exceptions | MAY | ||||
| Base Framework | Base Standard Profile | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Seq# | Data Element | Description | Flags | Optionality | Repetition | Length | C.LEN | Table | Data Type | Optionality | Table | |
| QRI |
||||||||||||
|
1 | 01436 | Candidate Confidence | O | 10# | NM Numeric |
||||||
|
2 | 01437 | Match Reason Code | O | Y | [2..2] | CWE Coded with Exceptions |
(0392) | ||||
|
3 | 01438 | Algorithm Descriptor | O | CWE Coded with Exceptions |
(0393) | ||||||
| Seq# | Data Element | Description | Optionality | Repetition | Length | C.LEN | Table | Data Type | |
|---|---|---|---|---|---|---|---|---|---|
| QRI |
|||||||||
|
1 | 01436 | Candidate Confidence | O | 10# | NM Numeric |
|||
|
2 | 01437 | Match Reason Code | O | Y | [2..2] | (0392) | CWE Coded with Exceptions |
|
|
3 | 01438 | Algorithm Descriptor | O | (0393) | CWE Coded with Exceptions |
|||
Definition: This field contains a numeric value indicating the match weight or confidence level associated with the record.
Example: |0.88| or |12.32|
One use of this optional field is in Patient Look-up transactions where the searching system employs a numeric algorithm for determining potential matches to patient/person look-ups.
Definition: This field contains a coded value indicating what search components (e.g., name, birth date, social security number) of the record returned matched the original query where the responding system does not assign numeric match weights or confidence levels. In short, it provides a method for passing a descriptive indication of why a particular record was found.
.Refer to User-defined Table 0392 - Match reason in Chapter 2C, Code Tables, for suggested values.
Definition: This field contains a text value indicating the name or identity of the specific search algorithm to which the RCP-5 Search confidence threshold and the QRI-1 Candidate confidence refer. Note that there are sometimes significant differences among the algorithms in their numeric scales (e.g., one is 0-100, another might be 10 - 20) as well as their meanings of the same value (two algorithms with an 80% match might not return the same records). Refer to User-defined Table 0393 - Match algorithms in Chapter 2C, Code Tables, for suggested values.
Example: |MATCHWARE_1.2^^HL70393| or |LINKSOFT_2.01^^HL70393|
One use of this optional field is in Patient Look-up transactions where the searching system employs a numeric algorithm for determining potential matches to patient/person look-ups.
The Demo site for our new HL7 Version 2+ (plus) Standard
