[Source] Add Quest Diagnostics
Closed this issue · 12 comments
According to Quest's website, they "touch" about 1/3 of Americans each year, so their reach is pretty large and would probably help be a draw for a number of users onto fasten.
That documentation is for their EHR platform, Quanum. It's not for the laboratory portion of Quest.
related fastenhealth/fasten-onprem#333
The Quest patient results FAQ has a dropdown that mentions a process for gaining access to the patient FHIR API. This leads to a request form, which, if filled out, sends an automated email to the requesting patient mentioning a process for integrating a new app with the Quest patient FHIR API. The pertinent information from the email is attached. In response, @AnalogJ has mentioned he is writing an email to Quest with the requested information, so we can further investigate API access.
Quick update: Quest is going to schedule a call with their development team next week.
moving to fasten-sources, where I'm tracking EHR platforms & integration statuses.
Update: Last communication was on April 2nd. Waiting on paperwork.
Quest Developer env requirements:
- HTTP Proxy & IP Allowlisting.
HTTP Proxy Alternatives:
Update: using AWS Workspaces + NAT Gateway for whitelisting
Update: Still waiting for Quest security team to finish their IP pen testing for Whitelisting
IP Testing has been completed. Waiting final approvals to begin API integrations.
time="2024-09-30T15:14:49Z" level=error msg="an error occurred while bulk importing resources from source: An error occurred during request https://api.questdiagnostics.com/resource-server/fhir/r4/Patient/xxxxxxxxxxx/$everything - 404 - 404 Not Found [{\"timestamp\":1727709289148,\"status\":404,\"error\":\"Not Found\",\"message\":\"No message available\",\"path\":\"/resource-server/fhir/r4/Patient/xxxxxxxxxx/$everything\"}]" type=ehi-export
use custom Patient everything path.