Online Consultation to Community Pharmacy - Pilot Specification

This version is in draft and is currently being migrated from the GP Connect Access Record: Structured specification

Release notes

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

0.2.0-alpha

Released on 20th December 2022 THIS VERSION CURRENT VERSION

Important: This guide has been forked from the GP Connect Send Document capability.

Changes

Removed "do not use" tags
  • The "do not use" tags contradict the profile cardinality and as such, have been removed to conform with the profile.
CareConnect-GPC-Patient-1
  • Updated to use the GP Connect variant of CareConnect-Patient-1 as the profile cardinality aligns closer to the use-case.
  • Added guidance around the usage of post code. It is optional in the profile; however, some consumers will reject a payload if a post code is not provided.

0.1.0-alpha

Released on 25th May 2022

Important: This guide has been forked from the GP Connect Send Document capability.

Link to specification


Changes

Forked specification
  • This specification has been forked from the GP Connect - Send Document capability to expiriment with sending structured data with FHIR, MESH, and ITK.
References to 1.4.0 and 1.5.x private-betas
  • both versions hosted, previously hosted on the NHS developer network, have now been removed
ITK3 Message Distribution standard
  • requirement to support version 2.10.0 from 2.5.0
All FHIR resources
  • clarified which elements are in UK Core vs CareConnect
ITK-Message-Bundle-1
  • clarified which elements should be populated along with examples
ITK-MessageHeader-2
  • clarified which elements should be populated along with examples
  • receiver must not be used
  • response must not be used
Extension-ITK-MessageHandling-2
  • clarification and guidance regarding this resource, along with examples
  • relaxed the requirements for extension(LocalExtension) to allow for any string
CareConnect-ITK-Header-Organization-1
  • clarified which elements should be populated along with examples
ITK-Document-Bundle-1
  • added optional support for replacement documents by including the version of the document within meta.versionId
  • clarified which elements of the profile should be used, along with examples - in particular around the section element
CareConnect-Composition-1
  • clarified which elements should be populated, along with examples
  • extension(careSettingTypeExtension) must not be used
  • class must not be used (it is not required and not in UK Core)
  • encounter must not be used
  • attester must not be used
  • event must not be used
  • expanded guidance on status and the possible values that could be contained within the code system
  • expanded guidance on type as multiple SNOMED codes can be used and mandated that this value MUST be used to identify the type of document being received, rather than the value provided in the MESH workflow ID, or LocalExtension value within the Extension-ITK-MessageHandling-2 resource
  • updated guidance to allow for any free-text string (not just a "Consultation Summary Report")
CareConnect-Patient-1
  • clarified which elements should be populated, along with examples
  • extension(ethnicCategory) must not be used
  • extension(religiousAffiliation) must not be used
  • extension(patient-cadavericDonor) must not be used
  • extension(residentialStatus) must not be used
  • extension(treatmentCategory) must not be used
  • extension(nhsCommunication) must not be used
  • extension(birthPlace) must not be used
  • extension(nominatedPharmacy) must not be used
  • extension(deathNotificationStatus) must not be used
  • active must not be used
  • telecom must not be used
  • gender must not be used
  • address can optionally be used
  • maritalStatus must not be used
  • multipleBirth must not be used
  • photo must not be used
  • contact must not be used
  • generalPractitioner can optionally be used
  • managingOrganization must not be used
  • link can optionally be used
CareConnect-Practitioner-1
  • clarified which elements should be populated, along with examples
  • extension(nhsCommunication) must not be used
  • active can optionally be used
  • address must not be used
  • gender must not be used
  • birthDate must not be used
  • photo must not be used
  • qualification must not be used
CareConnect-Organization-1
  • clarified which elements should be populated, along with examples
  • extension(mainLocation) must not be used
  • extension(organization-period) must not be used
  • active can optionally be used
  • type can optionally be used
  • alias can optionally be used
  • address can optionally be used
  • partOf must not be used
  • contact must not be used
  • endpoint must not be used
ITK-Attachment-Binary-1
  • clarification and guidance regarding MIME types, available extensions - along with examples
OperationOutcome
  • added clarification and guidance regarding this resource, along with examples
Other FHIR profiles payload requirements
How to configure MESH
  • clarification around using the element in the MESH configuration
How to handle updates to documents
  • clarification around terminology (replacement)
  • clarification on how to use version number
  • reference to ITK-Bundle-1 meta.versionId
back to top