GP Connect - Update Record (ITK3)

Release notes

Historical versions and their release notes can be found below, including links to the respective version of the specification.

1.1.4-public-beta

Released on Friday, 13th October 2023 THIS VERSION

Link to specification

Changes

Fixed red-flag example in PRSB headings section	Pointed to the incorrect clinical impression example - now resolved (2023/11/01)
BP Example 1 Updated	Added missing `meta.profile` to the Composition resource in the profile (2023/11/01).
Safeguarding flag	The flag for safguarding has been removed for iteration 1 as it further clinical guidance is required around how to flow the information digitally between pharmacy and GP systems.

1.1.3-public-beta

Released on Wednesday, 4th October 2023

Link to specification

Changes

Note: A minor update was made on 11/10/2023 to an error in the examples.
The details of which can be found below.

All examples	The wrong URL was shown in the examples for `ParticipantType` in the `Encounter` Changed from `https://fhir.nhs.uk/STU3/ValueSet/GPConnect-ParticipantType-1` to `https://fhir.nhs.uk/STU3/CodeSystem/GPConnect-ParticipantType-1` Updated Line 5 on all examples URL from `https://fhir.nhs.uk/STU3/StructureDefinition/ITK-Document-Bundle-1` to `https://fhir.nhs.uk/STU3/StructureDefinition/ITK-Message-Bundle-1`
Removal of "PFS and disclosure of information" section	The `NOPAT` code is ambigous since it is not clear as to whether it is clinician-led, or patient-led Further clinical guidance required before NHS England can provide appropriate guidance around how to appropriately handle patient requests for non-disclosure of information in patient-facing services This means that providers will not be sending the `NOPAT` code within the `meta.security` element, of the `CareConnect-GPC-Encounter-1` profile
Guidance added to MedicationDispense.type	Providers are recomended to populate this field with a code from the `https://fhir.hl7.org.uk/STU3/CodeSystem/CareConnect-MedicationSupplyType-1` code system

1.1.2-public-beta

Released on Thursday, 21st September 2023

Link to specification

Changes

Mapping PRSB headings to FHIR	Updated the pregnancy status example to use the correct code. Changed from `pregnancy-state` to `pregnancy-status`
Removed "Why not use meta.profile" section	No longer required.
Profile: CareConnect-Composition-1	Updated guidance to state that at least one Profile: CareConnect-GPC-ClinicalImpression-1 MUST be included as per PRSB Community Pharmacy Standard v3.01.
Command 'pagelink' could not render: Page not found.	Updated the example in `Encounter.meta.security.system` to `http://hl7.org/fhir/v3/ActCode`.
meta.profile	Updated the examples to include profile url in `meta.profile` of each fhir profile
Referencing ID's	Changed format of references within examples from `resource/[ID]` to `URN:UUID:[ID]`
FHIR package uplift to 1.1.3	FHIR package has been uplifted to version 1.1.3 to include additional items added to SDS job role ID and ITK message event code systems. Link to the new version of the package can be found by clicking here: Usage of FHIR packages

1.1.1-public-beta

Released on Thursday, 17th August 2023

Link to specification

Changes

FHIR package version uplift

The initial version of the FHIR package was not based on the Access Record: Structured FHIR assets which were created around five years before the publication date of this specification.
The FHIR package on Simplifier has been re-created, using gpconnect-fhir release/1.5.0 as a base.
Additional assets to support Update Record ITK3 have been added in this release.
This is the only change since previous published version of this specification, and the Usage of FHIR packages has been updated to reflect the change in package version number.
A link to the new package on Simplifier can be found by clicking here.

1.1.0-public-beta

Released on Tuesday, 8th August 2023

Link to specification

Changes

Handling vital-signs	Conventions around how vital signs are to be carried using this specification, and displayed.
Usage of FHIR packages	Information and signposting to the GPC Update Record FHIR package.
Profiles created	The following profiles have been created by the Interoperable Standards team within NHS England and added to this specification. Profile: CareConnect-GPC-MedicationDispense-1 Profile: CareConnect-GPC-ClinicalImpression-1
Handling identifiers	Clarification around usage over `urn:uuid:[id]` over `resourceName/[identifier]` for this specification.
Added example scenarios / ITK3 messages	Blood pressure check service - Example 1 Blood pressure check service - Example 2 Contraception service - Example 1 Contraception service - Example 2 Minor illness / Common conditions service - Example 1 Minor illness / Common conditions service - Example 2 A button to download an XML file has been added to each example. A button to allow a user to validate XML using Simplifier validation has been added to each example.
Code system: dm+d	Added reference to dm+d under codesystems.
Extension: Extension-ITK-MessageHandling-2	Guidance around usage of the `MessageDefinition` added.
Profile: ITK-Document-Bundle-1	Guidance around usage of `meta.lastUpdated` as per HL7 documentation added.
Resolved issue in guidance for MESH API: How to configure MESH	Previous guidance was incorrect and referenced the incorrect headers - this has been resolved a reference link to the MESH documentation has been added. Removed section around MESH and the use of version - while it can be populated, it cannot be reliably used to indicate the current version since the MESH API does not carry a concept of version.
Added Rejecting messages	Guidance added around reasons messages will be rejected. Guidance added around understanding the intent of a message.
Added Command 'pagelink' could not render: Page not found.	Section added to indicate how non-disclosure to linked profiles (proxy) can be relayed between clinical systems using `meta.security`.
Added Tagging payloads with meta.tag	Section added to indicate how tags can be used to provide additional context and information about a payload.
Added Profile: CareConnect-GPC-PractitionerRole-1	Links to the GP Connect Data model, included for reference.
Added Handling medications section	Guidance on how medications will be represented.
Added Value set: UCUM section	Reference to the Unified Code for Units of Measure value set.
Added Code system: RecordStandardHeadings section	Reference to the UK Core Record standard headings code system.
Updated Profiles section	Changed cardinality of `CareConnect-GPC-Observation-1` to `0..`. Changed cardinality of `CareConnect-GPC-MedicationDispense-1` to `0..` Updated name of `MedicationDispense` to `CareConnect-MedicationDispense-1`. Added intended delivery iterations and clarifications of all data-types required for the GP Matrix within the PRSB Community Pharmacy Standard.
Clarification on ingestion, filing, and workflow	Ingestion being all data items in the profiles section of this specification MUST BE auto-ingested - that is, the activity of mapping from the FHIR representation to the consumer (receivers) internal data model automatically (auto-ingest) without amendment, and appropriate elements shown within the same areas of the clinical system as they would be if they were created on the receiving system directly. Filing meaning that data is saved to the patient record in a "finalised" state. "Auto-filing" refers to the filing of clinical data without any engagement whatsoever. Workflow will be used initially for this capability as the auto-filing rules have not yet been established for the pharmacy services. More information can be found within the Workflow groups and ID section of this specification.
Mapping PRSB headings to FHIR	Formerly "How to represent uncategorised data". Usage of the UK Core Record Standings Code system. The code for the above system to be represented within `meta.tag`. Safeguarding can be represented within `CareConnect-Flag-1`. History can be represented within `ClinicalImpression`. Clinical Summary can be represented within `ClinicalImpression`. Signpost details can be represented within `ClinicalImpression`. Information and advice given can be represented within `ClinicalImpression`. Pregnancy status - * can be represented within `Careconnect-GPC-Observation-1`. Social context - * can be represented within `Careconnect-GPC-Observation-1`. Red flags can be represented as `ClinicalImpression`. Procedures and therapies - Procedures (ABPM declined) can be represented as `CareConnect-Observation-1`. Procedures and therapies - Contraception type can be represented as `CareConnect-GPC-Observation-1`.

1.0.0-public-beta

Released on Friday, 7th July 2023

Changes

Support for the following Pharmacy services:

Minor illnesses including common conditions
Blood pressure
Common conditions

1.0.0-draft

Released on 27th June 2023 DRAFT

Initial draft specification.