Filename structure: Extension-DataStandardsWales-[Descriptor]
id structure: Extension-DataStandardsWales-[Descriptor]

​ Worked example​
An extension to capture the digital status of a document in the DocumentReference resource.

Filename structure: MessageDefinition-DataStandardsWales-[MessageEvent]{-[Qualifier]}
id structure: DataStandardsWales-[MessageEvent]{-[Qualifier]}
Note that typically each message event would have one corresponding message definition. However, the FHIR standard does allow for multiple MessageDefinition resources with the same message event code. In this case a qualifier should be used.​

​ Worked example​
A message definition to submit a care document to a FHIR repository. The event code quoted will have been defined as part of a code system that is included in the bound DataStandardsWales-MessageEvent value set.

Filename structure: CodeSystem-DataStandardsWales-[Descriptor]
id structure: DataStandardsWales-[Descriptor]
Note that in line with UK and international practice the “CodeSystem” discriminator is omitted from id and name and from uses derived from those elements.​

​ Worked example​
A code system to define a set of concepts that describe the digital status of a document in the DocumentReference resource.

Filename structure: ValueSet-DataStandardsWales-[Descriptor]
id structure: DataStandardsWales-[Descriptor]
Note that in line with UK and international practice the “ValueSet” discriminator is omitted from id and name and from uses derived from those elements.​

​ Worked example​
A value set to specify the code systems that can be used to describe the digital status of a document in the DocumentReference resource.

Filename structure: NamingSystem-{[Organisation]}-{[System]}-[descriptor]
id structure: DataStandardsWales-{[Organisation]}-{[System]}-[Descriptor]
name structure: {[Organisation]}{[System]}[Descriptor]
uniqueId value structure:https://fhir.[ownerdomain]/Id/[Descriptor]

The formal convention is for Descriptor to be consistent between id, name and uniqueId, but the influence of external owners means this is not always the case. There is variability by owning system and organisation, as illustrated by the examples below.​

​ Worked example 1 - All Wales identifiers​
WRTS organization identifiers

LIMS TCLe report identifiers

Worked example 2 - Identifiers issued by local PAS​
PAS Practitioner Identifier (CAVUHB)

PAS Location Identifier (BCUHB)

Filename structure: Differentiator-[Owner][Descriptor]
id structure: [Owner][Descriptor]

​ Worked example​
A code system owned by the WPAS system classifiying source of admission.

Filename structure: [Example]-DataStandardsWales-[L3L4ResourceType]-[Descriptor]{-[Qualifier]}
id structure: [Example]-DataStandardsWales-[L3L4ResourceType]-[Descriptor]{-[Qualifier]}
reduced length id*: [Example]-DSW-[L3L4ResourceType]-[Descriptor]{-[Qualifier]}

*See the Character Restrictions section

​ Worked example 1​
An example Organization resource for Neath Port Talbot Hospital.

Worked example 2​
An example MedicationStatement resource for Bendroflumethiazide issued at the point of discharge.

The fields within a profile that store information are called elements. Any core element name is unchangeable and is dictated by HL7 and UK Core depending on who created the element. We can however create our own elements as extensions and slices. In all cases elements use the lowerCamelCase naming convention. e.g. DocumentReference.extension:digitalStatus

In the special case where a backport extension is used from a later FHIR release, the slice name for the extension is suffixed by the release number e.g. DocumentReference.extension:versionR5​

The following naming convention applies to the message event code as used by MessageDefinition.eventCoding and MessageHeader.eventCoding.

The event code should be lower case and follow the kebab-case naming convention e.g.

✅ patient-admission-submit  
❌ patientAdmission-submit  
❌ PatientAdmissionSubmit  

Event codes should be short and descriptive in the form [primary-content]-[qualifier]-[verb]

• primary-content → a high level description of the content in plain English and hyphenated (e.g. care-document, allergy-list, clinician)
• qualifier → optional detail (e.g. initial, amendment, discharge, lab)
• verb → action. Common verbs:
  • -submit: request to update if found, else create new.
  • -notify: informational event (server processes but does not persist resources).
  • -cancel: request to revoke/withdraw a prior submission.
  • -update: explicit update only (do not create if missing).

Examples WITHOUT qualifiers

• observation-submit
• allergy-list-update
• lab-result-notify

Examples WITH qualifiers

• observation-lab-submit
• observation-vitalsigns-update
  

Representation in event coding element:

"eventCoding": { 
"system": "https://fhir.nhs.wales/CodeSystem/DataStandardsWales-MessageEvent", 
"code": "care-document-submit",
"display": "Care Document Submit"
}