Description
Link explicit emergency order and result identifiers under a supplied system namespace.
Emergency records distinguish event clocks, retrospective entry times, equipment dates, encounter identifiers and recorded triage or laboratory states. A supplied time gap is not a verified performance measure, and a recorded seal expiry does not establish equipment readiness. Simulation duty fractions and role labels describe training records rather than emergency-care instructions.
Link explicit emergency order and result identifiers under a supplied system namespace.
When to use this tool
Use Emergency Order Result Identifier Pair when you already have orderId, resultId, sourceSystem and need to link explicit emergency order and result identifiers under a supplied system namespace.
How to use the tool and how it works
- Enter orderId, resultId, sourceSystem. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read token. Use the output convention below.
Enter orderId, resultId, sourceSystem using the field constraints below. Encode these values, in exactly that order, as a JSON array and return the serialized array as text in token. String values are preserved without trimming or external terminology lookup.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| orderId | Order Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| resultId | Result Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| sourceSystem | Source System | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | Token | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"orderId": "O17",
"resultId": "R4",
"sourceSystem": "SYS2"
},
"output": {
"token": "[\"O17\",\"R4\",\"SYS2\"]"
}
}Limitations and assumptions
- The result records supplied values without asserting clinical correspondence. Sources and asserted relationships are not independently authenticated.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Review the actual event, equipment and laboratory records with verified timing and the complete clinical workflow. Treat local flags and interval arithmetic as record checks; they do not supply triage, response protocols, safe staffing or an assessment of a real emergency.
References
Similar or alternative tools
- Emergency Training Role Tag
Label an explicitly assigned emergency-training role.
- Ambulance Equipment Checklist Revision Key
Encode an explicit ambulance checklist revision reference.