HL7 FHIR® CareConnect Profiles for STU3

This is the baseline of the FHIR CareConnect STU3 assets. The content will be refreshed dynamically as part of the development process for all changes or updates.


The goal of the CareConnect project is to adapt the HL7® FHIR® standard (version STU3) and create a library of profiles that implementers can adopt to simplify integration and interoperability within UK Health and Social Care.

Versioning of FHIR CareConnect Assets


This section details the versioning approach that will be applied for the baseline FHIR CareConnect Assets.

These Assets are:

URL and Name Format for Profiles

The URL format is defined as: 'URL' / 'FHIR asset type' / 'Resource ID'

For example:


URL and Profile Versioning

The FHIR assets will carry the major version information in the URL, but will use the internal version element as per the FHIR Standard. This is demonstrated below:

<StructureDefinition xmlns="http://hl7.org/fhir">
        <lastUpdated value="2018-03-28T13:59:04.782+01:00" />
    <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
        <valueCode value="pa" />
    <url value="https://fhir.hl7.org.uk/STU3/StructureDefinition/CareConnect-Patient-1" />
    <version value="1.3.0" />

Instance Conformance Identification

For some information flows, there is a requirement to identify which FHIR CareConnect profile(s) an ‘on the wire’ instance conforms to for the purpose of validation and/or conformance testing. This profile conformance is declared using the profile.meta element. This element carries the profile URL appended with the version information.

The format is: 'URL' "|" 'version'

For example:


This is illustrated below:

<Observation xmlns="http://hl7.org/fhir">
  <id value="f001"/>
        <profile value="https://fhir.hl7.org.uk/STU3/StructureDefinition/CareConnect-Observation-1|1.2.0" />

Command 'render' could not render: Sequence contains more than one element
NHSx-logo INTEROPen-logo PRSB-Logo