[Source] Add Quest Diagnostics

[samteezy]

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.

[RashKash103]

Documentation for their FHIR API

[hkamran80]

That documentation is for their EHR platform, Quanum. It's not for the laboratory portion of Quest.

[AnalogJ]

related fastenhealth/fasten-onprem#333

[beckyosb]

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.

[AnalogJ]

Quick update: Quest is going to schedule a call with their development team next week.

[AnalogJ]

moving to fasten-sources, where I'm tracking EHR platforms & integration statuses.

[AnalogJ]

Update: Last communication was on April 2nd. Waiting on paperwork.

[AnalogJ]

Quest Developer env requirements:

• HTTP Proxy & IP Allowlisting.

HTTP Proxy Alternatives:

• https://aws.amazon.com/blogs/networking-and-content-delivery/providing-controlled-internet-access-through-centralised-proxy-servers-using-aws-fargate-and-privatelink/
• http:https://www.squid-cache.org/Intro/
• https://github.com/dariubs/awesome-proxy
• https://github.com/tinyproxy/tinyproxy

[AnalogJ]

Update: using AWS Workspaces + NAT Gateway for whitelisting

[AnalogJ]

Update: Still waiting for Quest security team to finish their IP pen testing for Whitelisting

[AnalogJ]

IP Testing has been completed. Waiting final approvals to begin API integrations.