cds-prefetch-proxy

A generic proxy that takes the URL of an underlying service, and exposes a gateway in front of it.

This service exposes the CDS API calls and forwards them to the underlying service. In cases that preFetch data are expected, but not present, the proxy will assemble the required preFetchData.

Where possible, the proxy uses the CDS Validator library to validate the schemas of the requests or responses.

Tests for the API methods written cover the following expected behaviors:

GET /:actualServiceUrl/cds-services
  ✓ should forward the call to the upstream service and return the response to the client
  ✓ should return a 502 failure when the upstream service returns invalid json
  ✓ should return a 502 failure when there is an error with the upstream service

POST /:actualServiceUrl/cds-services/:serviceId
  ✓ should forward the call to the upstream service and return the response to the client
  ✓ should return a 400 failure when the client sends an invalid service request
  ✓ should return a 404 failure when the client tries to proxy a service that isnt discoverable
  ✓ should return a 502 failure when the upstream service returns invalid json
  ✓ should return a 502 failure when there is an error with the upstream service
  ✓ should not query the fhir server if prefetch data is included with the service request
  ✓ should query the fhir server if prefetch data is missing from the service request

POST /:actualServiceUrl/cds-services/:serviceId/analytics/:uuid
  ✓ should forward the call to the upstream service and return the response to the client
  ✓ should return a 502 failure when there is an error with the upstream service

Deployment

This proxy service can be deployed with Docker. By default, the Dockerfile exposes port 3000. Creating the Docker container can be done by:

$ docker build -t <your-name>/cds-hooks-prefetch-proxy .
Successfully built <container-id>

$ docker run -p 3000:3000 -d <your-name>/cds-hooks-prefetch-proxy npm start