Site identifier
HeyDonto FHIR R4 API - Terminology (1.0)
The Terminology Module provides an overview and guide to the FHIR resources, operations, coded data types and externally-defined standard and FHIR-defined terminologies that are used for representing and communicating coded, structured data in the FHIR core specification and profiles. Collectively, these capabilities are used to provide the terminology service functionality required for supporting the use of coded data in FHIR resources throughout the specification as described in the other modules.
The primary terminology-related structures and their relationships are shown below:

Example: Condition profile with Condition.code slice bound to "SNOMED CT fracture codes" value set
[Note: The ElementDefinition type (shown with a dotted box) is described elsewhere in the specification in the Foundation and Conformance modules.]
The Terminology Module covers the following:
Resources:
- CodeSystem - The CodeSystem resource is used to declare the existence of and describe a code system or code system supplement and its key properties, and optionally define a part or all of its content
- ValueSet - A ValueSet resource instance specifies a set of codes drawn from one or more code systems, intended for use in a particular context. Value sets link between CodeSystem definitions and their use in coded elements
- ConceptMap - A statement of relationships from one set of concepts to one or more other concepts - either concepts in code systems, or data element/data element concepts, or classes in class models
- NamingSystem - A curated namespace that issues unique symbols within that namespace for the identification of concepts, people, devices, etc. Represents a "System" used within the Identifier and Coding data types
- TerminologyCapabilities - A TerminologyCapabilities resource documents a set of capabilities (behaviors) of a FHIR Terminology Server that may be used as a statement of actual server functionality or a statement of required or desired server implementation
Terminology Service:
Operations:
CodeSystem:
ValueSet:
ConceptMap:
Coded Data Types:
Documentation:
For security considerations for terminology services, see the Terminology Service page Security section. For more general considerations, see the Security and Privacy module.
- Create or reference a code system
- Create or reference a value set
- Record data using pre-coordinated codes
- Record data using post-coordinated expressions
- Record data using multiple local or standard code systems (translations)
- Expand a value set
- Validate a code
- Look up a display term for a code
- Translate a code from one value set to another
- Maintain a client-side transitive closure table on subsumption relationships
- Test subsumption between concepts
- For a set of property/concept pairs, return the set of concepts for the requested properties
- Map data between different terminologies
- Declare the capabilities of a terminology service
The following terminology resources have been tested and are being used in production tooling and now are normative or are expected soon to progress to normative:
- ValueSet - Normative
- CodeSystem - Normative
- ConceptMap - Maturity Level 3
Other terminology resources are still in earlier stages of development. We intend to continue to develop and test these resources and advance them through the Maturity Levels at Connectathons and elsewhere:
- NamingSystem - Maturity Level 1
- TerminologyCapabilities - Maturity Level 0
https://docs.heydonto.com/_mock/apis/fhir/terminology/
https://api-staging.heydonto.com/
https://api.heydonto.com/
Sort the results by a given field, e.g. _sort=family or _sort=-date.
Restrict returned fields, e.g. _elements=identifier,name.
Filter by resource telecom, e.g. date=[SYSTEM]|[VALUE].
Search for resources by identifier token, e.g. identifier=http://hospital.org|12345.
Include related patient resources, e.g. patient=Patient/[id]&.
Reverse chaining, e.g. _has:Observation:subject:code=http://loinc.org|1234-5.
Search by tag on the resource meta, e.g. _tag=http://example.org/tags|sample-tag.
Search by security label on resource meta, e.g. _security=RBAC|CONFIDENTIAL.
- Mock server
https://docs.heydonto.com/_mock/apis/fhir/terminology/site/{siteId}/fhir/naming-system
- Sandbox
https://api-staging.heydonto.com/site/{siteId}/fhir/naming-system
- Production
https://api.heydonto.com/site/{siteId}/fhir/naming-system
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://docs.heydonto.com/_mock/apis/fhir/terminology/site/{siteId}/fhir/naming-system?_count=10&_page_token=CgYK...&_sort=family&_elements=identifier%2Cname&telecom=telecom%3Dphone%2C555-555-5555&_id=abc123&identifier=http%3A%2F%2Fhospital.org%2C12345&_include=string&patient=patient%3DPatient%2F%5Bid%5D%26&_revinclude=string&_has=Observation%3Asubject%3Acode%3Dhttp%3A%2F%2Floinc.org%2C1234-5&_tag=http%3A%2F%2Fexample.org%2Ftags%2Csample-tag&_security=RBAC%2CCONFIDENTIAL&_profile=http%3A%2F%2Fexample.org%2Ffhir%2FStructureDefinition%2Fcustom-profile' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'Any combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive.
The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
String of characters used to identify a name or a resource
A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents
An identifier - identifies some entity uniquely and unambiguously. Typically this is used for business identifiers.
Indicates the purpose of this bundle - how it is intended to be used.
An instant in time - known at least to the second
An integer with a value that is not negative (e.g. >= 0)
A series of links that provide context to this bundle.
An entry in a bundle resource - will either contain a resource or information about a resource (transactions and history only).
A signature along with supporting context. The signature may be a digital signature that is cryptographic in nature, or some other signature acceptable to the domain. This other signature may be as simple as a graphical image representing a hand-written signature, or a signature ceremony Different signature approaches have different utilities.
{ "resourceType": "Bundle", "type": "searchset", "total": 100, "link": [ { … }, { … }, { … }, { … } ], "entry": [ { … } ] }
Any combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive.
The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
String of characters used to identify a name or a resource
A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents
A human-readable summary of the resource conveying the essential clinical and business information for the resource.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
The status of this naming system. Enables tracking the life-cycle of the content.
Indicates the purpose for the naming system - what kinds of things does it make unique?
A date, date-time or partial date (e.g. just year or year + month). If hours and minutes are specified, a time zone SHALL be populated. The format is a union of the schema types gYear, gYearMonth, date and dateTime. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. Dates SHALL be valid dates.
Contact details to assist a user in finding and communicating with the publisher.
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.
A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine
The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate naming system instances.
A legal or geographic region in which the naming system is intended to be used.
Indicates how the system may be identified when referenced in electronic exchange.
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Identifies the unique identifier scheme used for this particular identifier.
- Mock server
https://docs.heydonto.com/_mock/apis/fhir/terminology/site/{siteId}/fhir/naming-system
- Sandbox
https://api-staging.heydonto.com/site/{siteId}/fhir/naming-system
- Production
https://api.heydonto.com/site/{siteId}/fhir/naming-system
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X POST \
'https://docs.heydonto.com/_mock/apis/fhir/terminology/site/{siteId}/fhir/naming-system' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"resourceType": "NamingSystem",
"id": "example",
"text": {
"status": "generated",
"div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n \n <p>\n <b>SNOMED CT</b>\n </p>\n \n <p> oid: 2.16.840.1.113883.6.96</p>\n \n <p> uri: http://snomed.info/sct</p>\n \n </div>"
},
"name": "SNOMED CT",
"status": "active",
"kind": "codesystem",
"date": "2014-12-13",
"publisher": "HL7 International on behalf of IHTSDO",
"contact": [
{
"name": "FHIR project team",
"telecom": [
{
"system": "url",
"value": "http://hl7.org/fhir"
}
]
}
],
"responsible": "IHTSDO & affiliates",
"description": "SNOMED CT is a concept-based, scientifically validated terminology that provides a unique and permanent concept identifier that can be included in multiple HL7 data types including CD and CE. The concepts are managed to avoid \"semantic drift\" so the meaning remains constant. If the concept is found to be ambiguous or the meaning changes, the concept is inactivated but still retained and the identifier is never reused. SNOMED CT'\''s concepts are interrelated hierarchically and using description logic. SNOMED CT concepts have a unique \"fully-specified name\", a preferred term, and, optionally, synonyms. The description languages include English and Spanish.",
"uniqueId": [
{
"type": "oid",
"value": "2.16.840.1.113883.6.96"
},
{
"type": "uri",
"value": "http://snomed.info/sct",
"preferred": true
}
]
}'Any combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive.
The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
String of characters used to identify a name or a resource
A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents
A human-readable summary of the resource conveying the essential clinical and business information for the resource.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
The status of this naming system. Enables tracking the life-cycle of the content.
Indicates the purpose for the naming system - what kinds of things does it make unique?
A date, date-time or partial date (e.g. just year or year + month). If hours and minutes are specified, a time zone SHALL be populated. The format is a union of the schema types gYear, gYearMonth, date and dateTime. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. Dates SHALL be valid dates.
Contact details to assist a user in finding and communicating with the publisher.
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.
A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine
The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate naming system instances.
A legal or geographic region in which the naming system is intended to be used.
Indicates how the system may be identified when referenced in electronic exchange.
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Identifies the unique identifier scheme used for this particular identifier.
{ "resourceType": "NamingSystem", "id": "example", "text": { "status": "generated", "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n \n <p>\n <b>SNOMED CT</b>\n </p>\n \n <p> oid: 2.16.840.1.113883.6.96</p>\n \n <p> uri: http://snomed.info/sct</p>\n \n </div>" }, "name": "SNOMED CT", "status": "active", "kind": "codesystem", "date": "2014-12-13", "publisher": "HL7 International on behalf of IHTSDO", "contact": [ { … } ], "responsible": "IHTSDO & affiliates", "description": "SNOMED CT is a concept-based, scientifically validated terminology that provides a unique and permanent concept identifier that can be included in multiple HL7 data types including CD and CE. The concepts are managed to avoid \"semantic drift\" so the meaning remains constant. If the concept is found to be ambiguous or the meaning changes, the concept is inactivated but still retained and the identifier is never reused. SNOMED CT's concepts are interrelated hierarchically and using description logic. SNOMED CT concepts have a unique \"fully-specified name\", a preferred term, and, optionally, synonyms. The description languages include English and Spanish.", "uniqueId": [ { … }, { … } ] }
- Mock server
https://docs.heydonto.com/_mock/apis/fhir/terminology/site/{siteId}/fhir/naming-system/{id}
- Sandbox
https://api-staging.heydonto.com/site/{siteId}/fhir/naming-system/{id}
- Production
https://api.heydonto.com/site/{siteId}/fhir/naming-system/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://docs.heydonto.com/_mock/apis/fhir/terminology/site/{siteId}/fhir/naming-system/{id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'Any combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive.
The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
String of characters used to identify a name or a resource
A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents
A human-readable summary of the resource conveying the essential clinical and business information for the resource.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
The status of this naming system. Enables tracking the life-cycle of the content.
Indicates the purpose for the naming system - what kinds of things does it make unique?
A date, date-time or partial date (e.g. just year or year + month). If hours and minutes are specified, a time zone SHALL be populated. The format is a union of the schema types gYear, gYearMonth, date and dateTime. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. Dates SHALL be valid dates.
Contact details to assist a user in finding and communicating with the publisher.
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.
A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine
The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate naming system instances.
A legal or geographic region in which the naming system is intended to be used.
Indicates how the system may be identified when referenced in electronic exchange.
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Identifies the unique identifier scheme used for this particular identifier.
{ "resourceType": "NamingSystem", "id": "example", "text": { "status": "generated", "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n \n <p>\n <b>SNOMED CT</b>\n </p>\n \n <p> oid: 2.16.840.1.113883.6.96</p>\n \n <p> uri: http://snomed.info/sct</p>\n \n </div>" }, "name": "SNOMED CT", "status": "active", "kind": "codesystem", "date": "2014-12-13", "publisher": "HL7 International on behalf of IHTSDO", "contact": [ { … } ], "responsible": "IHTSDO & affiliates", "description": "SNOMED CT is a concept-based, scientifically validated terminology that provides a unique and permanent concept identifier that can be included in multiple HL7 data types including CD and CE. The concepts are managed to avoid \"semantic drift\" so the meaning remains constant. If the concept is found to be ambiguous or the meaning changes, the concept is inactivated but still retained and the identifier is never reused. SNOMED CT's concepts are interrelated hierarchically and using description logic. SNOMED CT concepts have a unique \"fully-specified name\", a preferred term, and, optionally, synonyms. The description languages include English and Spanish.", "uniqueId": [ { … }, { … } ] }
Any combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive.
The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
String of characters used to identify a name or a resource
A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents
A human-readable summary of the resource conveying the essential clinical and business information for the resource.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
The status of this naming system. Enables tracking the life-cycle of the content.
Indicates the purpose for the naming system - what kinds of things does it make unique?
A date, date-time or partial date (e.g. just year or year + month). If hours and minutes are specified, a time zone SHALL be populated. The format is a union of the schema types gYear, gYearMonth, date and dateTime. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. Dates SHALL be valid dates.
Contact details to assist a user in finding and communicating with the publisher.
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.
A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine
The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate naming system instances.
A legal or geographic region in which the naming system is intended to be used.
Indicates how the system may be identified when referenced in electronic exchange.
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Identifies the unique identifier scheme used for this particular identifier.
- Mock server
https://docs.heydonto.com/_mock/apis/fhir/terminology/site/{siteId}/fhir/naming-system/{id}
- Sandbox
https://api-staging.heydonto.com/site/{siteId}/fhir/naming-system/{id}
- Production
https://api.heydonto.com/site/{siteId}/fhir/naming-system/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X PUT \
'https://docs.heydonto.com/_mock/apis/fhir/terminology/site/{siteId}/fhir/naming-system/{id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"resourceType": "NamingSystem",
"id": "example",
"text": {
"status": "generated",
"div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n \n <p>\n <b>SNOMED CT</b>\n </p>\n \n <p> oid: 2.16.840.1.113883.6.96</p>\n \n <p> uri: http://snomed.info/sct</p>\n \n </div>"
},
"name": "SNOMED CT",
"status": "active",
"kind": "codesystem",
"date": "2014-12-13",
"publisher": "HL7 International on behalf of IHTSDO",
"contact": [
{
"name": "FHIR project team",
"telecom": [
{
"system": "url",
"value": "http://hl7.org/fhir"
}
]
}
],
"responsible": "IHTSDO & affiliates",
"description": "SNOMED CT is a concept-based, scientifically validated terminology that provides a unique and permanent concept identifier that can be included in multiple HL7 data types including CD and CE. The concepts are managed to avoid \"semantic drift\" so the meaning remains constant. If the concept is found to be ambiguous or the meaning changes, the concept is inactivated but still retained and the identifier is never reused. SNOMED CT'\''s concepts are interrelated hierarchically and using description logic. SNOMED CT concepts have a unique \"fully-specified name\", a preferred term, and, optionally, synonyms. The description languages include English and Spanish.",
"uniqueId": [
{
"type": "oid",
"value": "2.16.840.1.113883.6.96"
},
{
"type": "uri",
"value": "http://snomed.info/sct",
"preferred": true
}
]
}'Any combination of letters, numerals, "-" and ".", with a length limit of 64 characters. (This might be an integer, an unprefixed OID, UUID or any other identifier pattern that meets these constraints.) Ids are case-insensitive.
The metadata about a resource. This is content in the resource that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
String of characters used to identify a name or a resource
A string which has at least one character and no leading or trailing whitespace and where there is no whitespace other than single spaces in the contents
A human-readable summary of the resource conveying the essential clinical and business information for the resource.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope.
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
The status of this naming system. Enables tracking the life-cycle of the content.
Indicates the purpose for the naming system - what kinds of things does it make unique?
A date, date-time or partial date (e.g. just year or year + month). If hours and minutes are specified, a time zone SHALL be populated. The format is a union of the schema types gYear, gYearMonth, date and dateTime. Seconds must be provided due to schema type constraints but may be zero-filled and may be ignored. Dates SHALL be valid dates.
Contact details to assist a user in finding and communicating with the publisher.
A concept that may be defined by a formal reference to a terminology or ontology or may be provided by text.
A string that may contain Github Flavored Markdown syntax for optional processing by a mark down presentation engine
The content was developed with a focus and intent of supporting the contexts that are listed. These contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate naming system instances.
A legal or geographic region in which the naming system is intended to be used.
Indicates how the system may be identified when referenced in electronic exchange.
May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Identifies the unique identifier scheme used for this particular identifier.
{ "resourceType": "NamingSystem", "id": "example", "text": { "status": "generated", "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n \n <p>\n <b>SNOMED CT</b>\n </p>\n \n <p> oid: 2.16.840.1.113883.6.96</p>\n \n <p> uri: http://snomed.info/sct</p>\n \n </div>" }, "name": "SNOMED CT", "status": "active", "kind": "codesystem", "date": "2014-12-13", "publisher": "HL7 International on behalf of IHTSDO", "contact": [ { … } ], "responsible": "IHTSDO & affiliates", "description": "SNOMED CT is a concept-based, scientifically validated terminology that provides a unique and permanent concept identifier that can be included in multiple HL7 data types including CD and CE. The concepts are managed to avoid \"semantic drift\" so the meaning remains constant. If the concept is found to be ambiguous or the meaning changes, the concept is inactivated but still retained and the identifier is never reused. SNOMED CT's concepts are interrelated hierarchically and using description logic. SNOMED CT concepts have a unique \"fully-specified name\", a preferred term, and, optionally, synonyms. The description languages include English and Spanish.", "uniqueId": [ { … }, { … } ] }
- Mock server
https://docs.heydonto.com/_mock/apis/fhir/terminology/site/{siteId}/fhir/naming-system/{id}
- Sandbox
https://api-staging.heydonto.com/site/{siteId}/fhir/naming-system/{id}
- Production
https://api.heydonto.com/site/{siteId}/fhir/naming-system/{id}
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X DELETE \
'https://docs.heydonto.com/_mock/apis/fhir/terminology/site/{siteId}/fhir/naming-system/{id}' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'{ "statusText": "OK", "status": 200 }
- Mock server
https://docs.heydonto.com/_mock/apis/fhir/terminology/site/{siteId}/fhir/naming-system/{id}/history
- Sandbox
https://api-staging.heydonto.com/site/{siteId}/fhir/naming-system/{id}/history
- Production
https://api.heydonto.com/site/{siteId}/fhir/naming-system/{id}/history
- curl
- JavaScript
- Node.js
- Python
- Java
- C#
- PHP
- Go
- Ruby
- R
- Payload
curl -i -X GET \
'https://docs.heydonto.com/_mock/apis/fhir/terminology/site/{siteId}/fhir/naming-system/{id}/history' \
-H 'Authorization: Bearer <YOUR_JWT_HERE>'{ "resourceType": "Bundle", "type": "history", "entry": [ { … } ], "total": 2 }