-
> The two approaches are never mixed within the same Topic - that is, all entries will either reference List(Category) or profiles representing the source record entries, but not both.
Suspect this…
-
We are including GMC numbers in our Practitioner responses.
These are being rejected with the following:
Message:
Shouldly.ShouldAssertException : identifier.System
should be on…
-
Simon to look at implementing the below scenarios into demonstrator. Will require Pete Salisbury to mock up a sample JSON payload.
1) includeConsultations request - when a patient has a consultatio…
-
Expand the statement:
"Provider systems SHALL record audit and provenance data in line with existing GPSoC framework agreements, including relevant IM1 requirements for interfacing mechanisms."
…
-
In order to prevent provider systems rejecting the register patient request message, consumer systems should apply the following formatting to patient telephone numbers added to that message:
Telec…
-
After speaking with the DDC it appears some of the described SSP functionality on the following page (Proxy section) was not developed and needs reviewing:
https://nhsconnect.github.io/gpconnect/in…
-
This is a placeholder issue assigned to no project. It has been raised to track issues that have been raised with the SSP via the DDC. Each issue will be updated as and when updates are available
*…
-
See also https://github.com/nhsconnect/nrls-reference-implementation/issues/4
Core issue is java libraries (HAPI FHIR) is defaulting to _format=xml which causes a 415 error from GP Connect. Have al…
-
1) Should a consumer perform an SDS lookup
* per interaction (per practice)?
* per capability (per practice)?
* once (per practice)?
2) What caching can be made on the results? Or should the…
-
There should be common PDS/DBS handling guidance for consumers which applies to all capabilities within GP Connect.
It should be written as a practical guide for consumers looking to use GP Connect…