Skip to content

GP Connect Send Document

This page tracks GP Connect Send Document as a distinct capability.

Onboarding check (8 September 2026): new developers can no longer onboard through GP Connect for Send Document, Update Record or Appointment Management; existing consumer suppliers can still onboard end users. Apply the current service boundary before treating a capability or DSIC standard as an available integration route.

Supported Conclusion

Send Document lets a point-of-care system send a document to the patient's registered GP practice, commonly a consultation summary after the patient has been seen in another care setting. NHS England Digital describes the product as using MESH to transfer a PDF created in the sending organisation's system into the receiver system, where it can be processed and filed.

Architecture Pattern

The developer-facing integration sends HL7 FHIR STU3 message payloads over MESH using ITK3, and NHS England Digital lists the integration as in production. It uses the GPFED_CONSULT_REPORT MESH workflow ID.

The developer specifications directory checked on 8 September 2026 lists Send Document 2.0.2, released 18 December 2024. This is distinct from the historical IRIS supplier-row cell v2.0.1; the specification listing does not prove a supplier has upgraded or is currently onboarded.

Evidence Status

Evidence status is high for NHS product and integration definition. Current capability evidence distinguishes the service-facing product page from the developer-facing FHIR/MESH integration detail; it is not proof that a specific supplier or care setting has enabled it.

Follow-up Evidence

  • Supplier progress for Send Document support.
  • Current InterSystems documentation mapping Health Connect or HealthShare to MESH/ITK3 Send Document routing.