GP Connect Send Document Due Diligence
This page tracks due-diligence requirements for GP Connect Send Document.
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_REPORTworkflow 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.
Related Pages
- GP Connect Due Diligence
- GP Connect Send Document
- GP Connect Update Record
- GP Connect Architecture Patterns
- GP Connect InterSystems Supplier Progress
Follow-up Evidence
- Current supplier-progress rows for Send Document.
- Current InterSystems documentation mapping Health Connect or HealthShare to MESH/ITK3 Send Document routing.
- Customer-side evidence showing live document sending and GP filing workflow.