Description
Record an attachment's declared media type and 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 an attachment's declared media type and source.
When to use this tool
Use Clinical Attachment Media Type Label when checking the stated restricted health-data record, token or transition convention.
How to use the tool and how it works
- Enter attachmentId, suppliedMediaType, sourceRecord. 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 attachment ID, supplied media type and source record. Encode the ordered triple as JSON text.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| attachmentId | Attachment Id | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| suppliedMediaType | Nonempty unparsed label; neither MIME syntax nor attachment bytes are inspected. | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| sourceRecord | Source Record | 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": {
"attachmentId": "A17",
"suppliedMediaType": "application/pdf",
"sourceRecord": "R4"
},
"output": {
"token": "[\"A17\",\"application/pdf\",\"R4\"]"
}
}Limitations and assumptions
- Media-type syntax and attachment bytes are not inspected; the label does not establish file safety or correct content type.
- 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
- Clinical Code System Edition Key
Keep a clinical code, code system and edition together as a record key.
- Clinical Unit Code Namespace Label
Identify a clinical unit code by its namespace and version.