I’m developing an integration to the PDS FHIR API (Application Restricted mode) .
So far I’ve pointed my application at the Sandbox environment, but the data there seems quite limited.
My company is currently working through the onboarding process, but I’m wondering at what point can I access the Integration Test API - e.g. do I need to await approval for our application, or can I just point my application at the integration URLs and expect it to work?
I also have a specific question on the behaviour of the API (which may be due to using the sandbox API) : Using the example from the postman collection, a basic search uses eq as part of the birthdate: /Patient?family=Smith&gender=female&birthdate=eq2010-10-22
The HAPI FHIR Client library I’m using would not include the eq as part of the birthdate: /Patient?family=Smith&birthdate=2010-10-22&gender=female
From my reading of the FHIR spec, the two calls ought to be equivalent. Is this a limitation of the Sandbox API, or is there a meaningful difference between the two calls?
Do I need to await approval for our application, or can I just point my application at the integration URLs and expect it to work?
The former: you need to await for your application to reach the appropriate point of approval. The onboarding team will be better placed to give you a more specific point at which you will be given access to the integration environment.
(re eq in birthdate search) Is this a limitation of the Sandbox API, or is there a meaningful difference between the two calls?
Thank you for spotting this, I shall raise a ticket.
It is worth noting that the sandbox is built as the starting point to understand the shape of responses from this API, rather than a mock that thoroughly mimics the API’s behaviour. For that you will need to wait until you have access to the integration environement.
Hi David, many thanks for responding! That’s incredibly useful to know what to expect with the Sandbox API. I think canned responses are all good when getting a feel for things, but I’ll await access to the INT APIs for more in-depth testing.
Thanks for raising a ticket for the Sandbox eq matching - that one would be useful to have - even though sandbox is limited, I was previously able to create a Jane Smith with the correct birthdate in my system and trigger a demographic lookup, which was a useful initial proof-of-concept.
I’ll contact the onboarding team to ask when we’d be likely to get access to the INT APIs.