GP Connect 1.4.0-beta released on 7th May 2021

Release overview

The GP Connect Messaging 1.4.0-beta release is a patch release including:

• additional use case to support Online Consultation Reports - sending an online consultation back to the patient’s registered GP practice, or to a patient selected alternative care provider. A PDF must be sent, but additional FHIR resources can be populated.
• Send Document payload has been updated to contain the following FHIR resources:
  • GPConnect-Device-1
  • CareConnect-List-1
  • CareConnect-Observation-1
  • CareConnect-QuestionnaireResponse-1
  • CareConnect-Location-1
  • ITK-Document-Bundle
  • CareConnect-Composition-1
  • ITK-Attachment-Binary-1
  • CareConnect-Patient-1
  • CareConnect-Organization-1
  • CareConnect-Practitioner-1
  • CareConnect-RelatedPerson-1
  • ITK-Device-1
  • CareConnect-Encounter-1
  • CareConnect-List-1
  • CareConnect-Observation-1
  • CareConnect-Questionnaire-1
  • CareConnect-QuestionnaireResponse-1
  • CareConnect-ReferralRequest-1
  • CareConnect-DocumentReference-1
  • CareConnect-AllergyIntolerance-1
  • CareConnect-FamilyMemberHistory-1
  • CareConnect-Task-1
  • CareConnect-Consent-1

Important: All requirements listed in 1.4.0 have been renumbered to align with core Send Document requirements and specific use case requirements.

Page-by-page breakdown of changes

Pages updated to support new use cases:

• Introduction to GP Connect Messaging
• Spine integration illustrated
• Integration to MESH
• Send Document - Introduction
• Send Document - Message payload

Pages added to support Online Consultation Report use case:

• Overview
• Process map
• User stories
• Clinical engagement
• Payload requirements
• ITK3 header requirements
• MESH message configuration
• Triggering message creation
• Message example

Updates made during beta

• Send Document payload has been updated to contain the following FHIR resources:
  • CareConnect-Location-1

Pages updated to location resource:

• Send Document - Message payload
• Payload requirements

Alignment with 1.3.1 patch release

• MESH message configuration
  • GPCM-SD-CS-079 added - LocalID MUST contain the ODS code of the sending organisation
  • GPCM-SD-CS-080 added - Mex-Localid MUST contain the ODS code of the sending organisation
• MESH message configuration
  • GPCM-SD-OC-174 added - LocalID MUST contain the ODS code of the sending organisation
  • GPCM-SD-OC-175 added - Mex-Localid MUST contain the ODS code of the sending organisation