Description
Record a health-record subject reference and its assigning source.
Health-information systems separate identifiers, code-system namespaces, source versions, missing-value states and reference syntax. Recording a mapping or recognizing a restricted token does not validate its clinical meaning or a complete HL7/FHIR resource. Explicit null, empty text, unknown status and numeric zero are different states.
Record a health-record subject reference and its assigning source.
When to use this tool
Use Health Record Subject Reference when checking the stated restricted health-data record, token or transition convention.
How to use the tool and how it works
- Enter recordCode, subjectReference, assigningSource. 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.
Require nonempty record code, subject reference and assigning source. Encode them in that order as JSON text.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| recordCode | Record Code | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| subjectReference | Subject Reference | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| assigningSource | Assigning Source | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| token | JSON-encoded ordered tuple or literal token under the convention above; not a database lookup or authentication result. | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"recordCode": "OBS17",
"subjectReference": "Patient/p17",
"assigningSource": "System A"
},
"output": {
"token": "[\"OBS17\",\"Patient/p17\",\"System A\"]"
}
}Limitations and assumptions
- A subject link is a supplied assertion; no resource lookup, identity resolution or record-access permission is checked.
- 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
Use the intended complete interoperability specification, authoritative terminology and verified source records for actual resource validation, semantic mapping or clinical use.
References
Similar or alternative tools
- Health Record Retracted Result Link
Link a clinical result identifier to a supplied retraction-record identifier.
- Health Care Consent Purpose Code
Record a health-consent purpose code together with its coding system.