[GPCAPIM-242]-[Prepare Manual API test for demonstrator Get Patient Record]-[RP] #36
Conversation
| @@ -0,0 +1,3 @@ | |||
| vars { | |||
| environment: 127.0.0.1:8080 | |||
There was a problem hiding this comment.
we have port 8080 in this file and in the mock-response.js file - can we store it in one place and share it?
There was a problem hiding this comment.
ah from reading up i am not sure that its possible - feel free to resolve this if you find the same
There was a problem hiding this comment.
ok thanks
| } | ||
|
|
||
| get { | ||
| url: http:// |
There was a problem hiding this comment.
does this need filling out?
There was a problem hiding this comment.
I'm deleting this one and we can re-add when we have more environment info
| Ssp-To: 918999198738 | ||
| Accept: application/fhir+json | ||
| Ssp-InteractionId: urn:nhs:names:services:gpconnect:fhir:operation:gpc.getstructuredrecord-1 | ||
| Authorization: Bearer {{jwt_token}} |
There was a problem hiding this comment.
is there something somewhere to set
{{jwt_token}}
There was a problem hiding this comment.
Not yet - I left it in until we had an environment to use it on and then tidy the headers up from there
BJSS-russell-pollock
force-pushed
the
feature/GPCAPIM-242
branch
from
da0e209 to
cb5f0e9
Compare
|
2 participants
Description
As a Tester
I want to investigate and assess the GP Connect Demonstrator Get Patient Resource endpoint for potential use in the Steel Thread Get Patient Resource work.
So that we can set up what we believe is the correct response body structure and enable a simple manual API test to support preparation. We are not proving anything at this stage.
Context
GP Connect demonstrator has an existing endpoint that is capable of retrieving a FIHR STU3 patient resource by patient id https://orange.testlab.nhs.uk/
Checklist
Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.