GP Connect Due Diligence
This section mirrors the GP Connect Capability Map. Use it for capability-specific implementation, assurance, and evidence checks after identifying the relevant GP Connect capability.
Due Diligence Map
| Capability | Due-diligence page | Main check |
|---|---|---|
| Access Record: HTML | Access Record HTML Due Diligence | Confirm read-only HTML view scope, SSP route, registered-GP lookup, and supplier/provider rollout. |
| Access Record: Structured | Access Record Structured Due Diligence | Confirm HSCN, SSP, RBAC/JWT, TLS MA, testing, onboarding, and supported structured record areas. |
| Access Document | Access Document Due Diligence | Confirm document-search/retrieval scope, SSP route, document-reference handling, and pilot/rollout status. |
| Send Document | Send Document Due Diligence | Confirm MESH/ITK3/FHIR STU3 route, PDF summary behaviour, workflow ID, and receiver filing process. |
| Update Record | Update Record Due Diligence | Confirm the restricted community-pharmacy workflow, MESH route, clinical-safety obligations, and assured suppliers. |
| Patient Facing APIs | Patient Facing APIs Due Diligence | Confirm NHS API Platform route, NHS App/current consumer constraints, provider eligibility, and patient-facing access scope. |
Interpretation
Capability pages answer "what is this GP Connect capability?" Due-diligence pages answer "what must be checked before relying on this capability in a product, supplier, or deployment claim?"
For InterSystems analysis, a due-diligence page is NHS requirement context rather than proof of InterSystems support. Product-level claims require InterSystems documentation, NHS supplier-progress evidence, or customer deployment evidence for the specific product and capability.