Description
Record a health-consent purpose code together with its coding system.
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-consent purpose code together with its coding system.
When to use this tool
Use Health Care Consent Purpose Code when checking the stated restricted health-data record, token or transition convention.
How to use the tool and how it works
- Enter consentRecord, purposeCode, purposeSystem. 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 consent-record label, purpose code and purpose system. Encode those three values as JSON text.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| consentRecord | Consent Record | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| purposeCode | Supplied purpose token, not a valid-consent or authorization decision. | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| purposeSystem | Purpose System | 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": {
"consentRecord": "C17",
"purposeCode": "research",
"purposeSystem": "urn:local:purposes"
},
"output": {
"token": "[\"C17\",\"research\",\"urn:local:purposes\"]"
}
}Limitations and assumptions
- A recorded purpose code does not establish informed consent, valid processing authority or actual permission to disclose health data.
- 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 Record Subject Reference
Record a health-record subject reference and its assigning source.