Documents - Multiple calls to ID patient and document

nhsconnect / gpconnect

GP Connect API specification

https://digital.nhs.uk/services/gp-connect/gp-connect-specifications-for-developers

Apache License 2.0

34 stars 26 forks source link

Documents - Multiple calls to ID patient and document #851

Closed Fitz1006 closed 5 years ago

Fitz1006 commented 5 years ago

TPP - Annelie - https://developer.nhs.uk/apis/gpconnect-documents-1-0- /accessrecord_documents_development_api_session.html Documents Why do TPP need to do the first call to find the patient and then a second call to query the documents? Why not do both in one as Structured Meds and Allergies does at the moment?

Fitz1006 commented 5 years ago

Updated to V1.4.1 from V1.4.0

dilrajbhatia2 commented 5 years ago

@mstephens-xsl Hi Matt, please could you look into this query.

mstephens-xsl commented 5 years ago

The find patient API has been added to locate the logical id for a patient from a provider. This is then used in the search Document API. This follows the RESTful API that has been implemented for appointment management, the single call approach for structured wasn't used as structured uses a FHIR operation and not a RESTful API.