Automated Update from Simplifier

guides/UK-Core-Implementation-Guide-STU3-Sequence/Home/Guidance/Identifier-Guidance/Index.page.md

@@ -0,0 +1,72 @@
+# {{page-title}}
+
+<div id="newAsset" markdown="span" class="alert alert-success" role="alert"><h4><i class="fa fa-star">
+<h2> Principles</h2>
+The following principles apply to the definition and use of identifier systems within UK Core–conformant implementations:
+
+
+- Uniqueness is the primary requirement for an identifier system, although excessive specialisation reduces long‑term usefulness and semantic value.
+
+
+- Identifier systems SHOULD NOT carry meaning. Consumers SHOULD NOT derive semantics from the structure or contents of the system or value. Identifier systems exist solely to establish uniqueness and scope.
+
+- Ownership of identifiers SHOULD be clear.
+Ideally, the system generating the identifier is represented by a unique identifier system URI. Where this is not possible, the organisation that owns and manages the identifiers should be considered the authority for that system.
+
+
+- Identifier system URIs MAY change over time.
+Implementations SHOULD NOT assume system URIs are permanently resolvable or immutable. Most healthcare data has a limited operational lifespan, and identifier systems may evolve accordingly.
+
+
+- Use of the NamingSystem resource is OPTIONAL.
+NamingSystem resources are intended for historical reference and documentation only. Implementations SHOULD NOT rely on the presence of a NamingSystem for runtime processing or validation.
+
+
+- Do not rely on assigner or type for processing or search.
+Best practice is to avoid dependence on Identifier.assigner or Identifier.type, as neither element is reliably searchable across implementations.
+
+See <a href="https://build.fhir.org/datatypes.html#Identifier">DataTypes - Identifier</a> and <a hred="https://build.fhir.org/ig/HL7/fhir-for-fair/FHIRidentifiers.html>FHIR for FAIR - FHIR Identifiers</a>for more information
+
+<h2>Identifier System Preferred Approach</h2>
+
+Where a recognised identifier system exists, or one can reasonably be established:
+
+Systems SHOULD use the published identifier system as the default.
+The system URI SHALL uniquely identify the namespace in which identifier values are issued.
+
+Vendor‑Defined Identifier Systems
+Where no nationally or regionally defined identifier system exists:
+
+Suppliers MAY define their own identifier system using a vendor‑controlled URI.
+The URI DOES NOT NEED to be resolvable, but SHALL be globally unique.
+Responsibility for uniqueness and lifecycle management rests with the defining vendor.
+
+Organisational Fallback Pattern
+If neither a standard nor vendor‑defined system is available, the following organisational pattern MAY be used:
+
+```json
+identifier: [
+    {
+    system: <org-id-system>/<org-code>/<specialism>,
+    value: <local-id>
+    }
+]
+``` 
+
+
+Example
+
+```json
+identifier: [
+    {
+    system: https://fhir.nhs.uk/Id/ods-site-code/1234/pathology-specimenvalue,
+    value: R1234
+    }
+]
+``` 
+
+
+The system URI defines the organisational and functional scope.
+The value is unique only within that system.
+Consumers MUST NOT interpret meaning from either the system path or the identifier value.
+</div>

guides/UK-Core-Implementation-Guide-STU3-Sequence/Home/Guidance/Identifier-Guidance/toc.yaml

@@ -0,0 +1,2 @@
+- name: Index
+  filename: Index.page.md

guides/UK-Core-Implementation-Guide-STU3-Sequence/Home/Guidance/toc.yaml

@@ -10,3 +10,5 @@
   filename: MustSupport-Guidance
 - name: Lifecycle
   filename: Lifecycle
+- name: Identifier Guidance
+  filename: Identifier-Guidance

guides/UK-Core-Implementation-Guide-STU3-Sequence/Home/ProfilesandExtensions/Profiles-Index.page.md

@@ -30,6 +30,33 @@ In addition, each Profile also has the following:
 
 </div>
 
+## Core Profiles
+
+<div class="tab">
+  <button class="tablinks active" onclick="openTab(event, 'profiles')">Profiles</button>
+  <button class="tablinks" onclick="openTab(event, 'derived-profiles')">Derived Profiles</button>
+  <button class="tablinks" onclick="openTab(event, 'profiles-with-purpose')">Profiles with Info</button>
+  <button class="tablinks" onclick="openTab(event, 'derived-profiles-with-purpose')">Derived Profiles with Info</button>
+</div>
+
+<div id="profiles" class="tabcontent" style="display:block">
+  {{page:Profiles-Table}}
+</div>
+
+<div id="derived-profiles" class="tabcontent" style="display:none">
+  {{page:Derived-Profiles-Table}}
+</div>
+
+<div id="profiles-with-purpose" class="tabcontent" style="display:none">
+  {{page:Profiles-Table-With-Purpose}}
+</div>
+
+<div id="derived-profiles-with-purpose" class="tabcontent" style="display:none">
+  {{page:Derived-Profiles-Table-With-Purpose}}
+</div>
+
+## Derived Profiles
+
 <div class="tab">
   <button class="tablinks active" onclick="openTab(event, 'profiles')">Profiles</button>
   <button class="tablinks" onclick="openTab(event, 'derived-profiles')">Derived Profiles</button>

guides/UK-Core-Implementation-Guide-STU3-Sequence/Home/Terminology/Terminology-Index.page.md

@@ -18,6 +18,28 @@ Other ValueSets are usable if the binding strength is defined as extensible. For
 Within this release of the UK Core, ValueSet expansions have been incorporated into the ValueSets. For some ValueSets containing SNOMED CT or dm+d data in particular, the number of concepts were deemed too large to expand. It should also be remembered that the expansions of SNOMED CT data in particular represent the content available at the time the expansion was generated, but that this content can subsequently change. For an up to date and complete list of values, suppliers SHOULD consult the latest SNOMED CT terminology release.
 </div>
 
+<div id="newAsset" markdown="span" class="alert alert-success" role="alert"><h4><i class="fa fa-star"></i>
+<h2> SNOMED CT UK Edition</h2>
+
+The FHIR UK Core terminology bindings utilise the UK Edition of SNOMED CT. This edition includes the International release of SNOMED CT, supplemented by UK-specific clinical concepts, reference sets, and descriptions that reflect the needs of health and care services across the United Kingdom. 
+
+
+UK Core mandates the use of SNOMED CT, specifically the SNOMED CT UK Edition, for all clinical concepts where SNOMED CT is indicated.
+All UK Core profiles, value sets, and examples that reference SNOMED CT SHALL be interpreted using the SNOMED CT UK Edition.
+
+SNOMED CT International URI:  
+    `http://snomed.info/sct`  
+
+SNOMED CT UK Edition URI:  
+    `http://snomed.info/sct/83821000000107`
+
+
+Implementations claiming conformance to UK Core SHALL support the latest version of the SNOMED CT UK Edition and any UK‑specific reference sets used by UK Core artefacts.
+
+The latest release can be accessed via:
+- the [The NHS England terminology server](https://digital.nhs.uk/services/terminology-server), or
+- the [NHS England TRUD](https://isd.digital.nhs.uk/trud/users/guest/filters/0/home) (Technology Reference data Update Distribution) service
+</div>
 
 <style>
  [class*=override] {