HL7 FHIR® UK Core Design and Development Approach

Metadata Design

This section describes the approach taken for metadata relating to the resources used within the UK Core.

File Format

All Resources SHALL be in the XML format and stored within GitHub. Snapshots SHALL NOT be used in any assets. All Profiles and Extensions SHALL be created using Firely Forge. The setting for the snapshot component in Forge, SHALL be deselected from the Options menu.

Properties

Filename format The filename SHALL be human readable with a maximum character limit of 64 digits. The physical filename format to be used for these assets is as below, where [Name] is in PascalCase:

  • Profile: UKCore-[Name].xml
  • Extension: Extension-UKCore-[Name].xml
  • ValueSet: ValueSet-UKCore-[Name].xml
  • CodeSystem: CodeSystem-UKCore-[Name].xml
  • ConceptMap: ConceptMap-UKCore-[Name].xml

url property The url format to be used for these assets is as below, where [Name] is in PascalCase:

  • Profile: https://fhir.hl7.org.uk/StructureDefinition/UKCore-[Name]
  • Extension https://fhir.hl7.org.uk/StructureDefinition/Extension-UKCore-[Name]
  • ValueSets: https://fhir.hl7.org.uk/ValueSet/UKCore-[Name]
  • CodeSystems: https://fhir.hl7.org.uk/CodeSystem/UKCore-[Name]
  • ConceptMaps: https://fhir.hl7.org.uk/ConceptMap/UKCore-[Name]

Common properties

  • id: UKCore-[Name] - [Name] is in PascalCase
  • name: UKCore[Name] - [Name] is in PascalCase
  • title: UK Core [Name][Name] is in Proper Case
  • status: draftunless stated otherwise

NOTE: The [Name], and specifically the id, must not contains any . characters.


NamingSystem.status

The following status values SHALL be used for all assets:

  • draft - Assets in development.
  • active - Assets that have been approved via Clinical and Technical Assurance (C&TA).
  • retired - Assets that are no longer required, after discussion from C&TA or Ballot process.

Note: when the status changes, such as draft to active, or to retired, the date SHALL also be updated. The version number SHALL stay the same, unless other amendments are carried out to the asset. Retired assets SHALL NOT be deleted from GitHub.

Note: draft assets should be created with a version of 0.0.1


back to top