| baseUrl |
A fixed value of https://fhir.nhs.wales applies to all resource definitions in the Wales FHIR Implementation Guide. |
| BusinessName |
The business name of the resource. Constructed according to rules specific to the resource type. UpperCamelCase used for each contributing element. |
DataStandardsWales |
This fixed value indicates that this is a Wales-wide standard, equally applicable to exchange or storage of FHIR data in any system in Wales. |
| Descriptor |
A simple descriptor for the subject of the resource definition. For CodeSystem and ValueSet, where applicable, this shall reflect the name given to the data set as published in the relevant Data Standards Change Notice (DSCN). For ConceptMap resources, this shall reflect the name given to the value set that is being mapped to or from. |
| Discriminator |
This is used to distinguish one FHIR asset type from another. It is typically the Level 2 HL7 resource type such as CodeSystem, but it is also used to distinguish Profile from Extension as both are instances of the StructureDefinition resource type. |
| L2ResourceType |
The Level 2 FHIR resource type. The resource definitions covered by this section are of the following types: StructureDefinition, MessageDefinition, CodeSystem and ValueSet. ConceptMap and NamingSystem definitions are covered separately in the “Additional naming conventions” section below. |
| L3L4ResourceType |
The Level 3 or Level 4 resource type e.g.‘Patient’, ‘Organization’, ‘Observation’, ‘Medication’. |
| MessageEvent |
The code for the message event, converted from kebab-case to UpperCamelCase. |
| Organization |
A recognised abbreviation for the organisation that owns the namespace. |
| Owner |
A recognised abbreviation for the system or organisation that owns the terminology asset. |
| Qualifier |
Used as an additional descriptor when existing resources are specialised for a specific use case. |
| System |
A recognised abbreviation for the system that owns the namespace. |
| .xml |
Resources are defined using xml to ensure that the correct element order is made explicit for resource instances created using xml. The json equivalent is published via conversion from xml in the implementation guide. |
