Description
Parse exactly an uppercase-leading alphanumeric resource-type token, slash, and 1-64 ASCII letters, digits, dots, or hyphens for logicalId.
Clinical identifiers and references have a namespace, target, and sometimes a version or contained-resource scope. Parsing their spelling does not resolve the target or establish semantic identity.
Parse exactly an uppercase-leading alphanumeric resource-type token, slash, and 1-64 ASCII letters, digits, dots, or hyphens for logicalId.
When to use this tool
Use FHIR Reference Relative Type ID when you need one supported clinical-reference or scoped-identifier component.
How to use the tool and how it works
- Enter reference. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read resourceType, logicalId. Use the output convention below.
Parse exactly an uppercase-leading alphanumeric resource-type token, slash, and 1-64 ASCII letters, digits, dots, or hyphens for logicalId.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| reference | Supplied reference token under the supported grammar. | Required. Text; maximum UTF-16 length 8192. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| resourceType | Resource Type | Required. Text; maximum UTF-16 length 8192. |
| logicalId | Logical Id | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"reference": "Patient/001-A"
},
"output": {
"resourceType": "Patient",
"logicalId": "001-A"
}
}Limitations and assumptions
- This narrow relative grammar excludes absolute, contained, and version-history references; resource type spelling and target existence are not verified against a FHIR registry or server.
- 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 a complete standard-aware resolver and verify terminology, resource identity, and applicable profiles separately.
References
Similar or alternative tools
- FHIR Reference Version History Token
Parse a supported relative ResourceType/id with optional /_history/version, using 1-64 ASCII identifier characters.
- FHIR Reference Target Token
For a leading hash, validate the remaining 1-64-character identifier and return it as a contained target with empty resourceType.