Skip to content

GP Connect Send Document Due Diligence

This page tracks due-diligence requirements for GP Connect Send Document.

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.

Use GP Connect Send Document for the capability definition. This page is the implementation and assurance checklist.

Why It Matters

Send Document is a document-sending workflow from a point-of-care system to the patient's registered GP practice. NHS material describes current behaviour around PDF consultation summaries sent over MESH, not generic structured write-back.

NHS Implementation Controls

NHS evidence points to these checks:

  • Confirm the sending care setting, receiver GP practice workflow, and direct-care basis for sending the document.
  • Confirm MESH, ITK3, HL7 FHIR STU3 payload handling, and the GPFED_CONSULT_REPORT workflow ID.
  • Confirm how the sending system creates the PDF summary and how the receiving GP system processes and files it.
  • Confirm supplier-progress status for both sending/consumer and receiving/provider systems before assuming live capability.
  • Confirm local operational handling for failures, duplicates, filing queues, audit, and clinical-safety ownership.

Evidence Status

Confidence is high for NHS product and integration definition. This page does not prove InterSystems support or local MESH/ITK3 configuration in a named deployment.

Follow-up Evidence