Description
Attach a caller-declared precision label to FHIR-related timestamp text.
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.
Attach a caller-declared precision label to FHIR-related timestamp text.
When to use this tool
Use FHIR Timestamp Precision Tag when checking the stated restricted health-data record, token or transition convention.
How to use the tool and how it works
- Enter timestampText, recordedPrecision. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read tag. Use the output convention below.
Require nonempty timestamp text and a recordedPrecision token from year, month, day, second, fractional-second or unknown. Encode [timestampText,recordedPrecision] as JSON text.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| timestampText | Timestamp Text | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| recordedPrecision | Caller-declared precision; no inference from timestampText or full FHIR temporal validation. | Required. Text; one of "year", "month", "day", "second", "fractional-second", "unknown"; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| tag | Tag | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"timestampText": "2026-11-01",
"recordedPrecision": "day"
},
"output": {
"tag": "[\"2026-11-01\",\"day\"]"
}
}Limitations and assumptions
- Precision is declared, not inferred; timestamp syntax, timezone and actual FHIR temporal validity are not 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
- HL7 Null Empty Value Distinction
Distinguish the raw HL7 two-quote null indicator, empty text and other values.
- Clinical Datetime Offset Known Flag
Expose whether a supplied clinical datetime offset is known and can be applied.