-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Ingress Endpoint Implementation #319
Ingress Endpoint Implementation #319
Conversation
Signed-off-by: Dixon Whitmire <[email protected]>
Signed-off-by: Dixon Whitmire <[email protected]>
Signed-off-by: Dixon Whitmire <[email protected]>
with open(file_path, "r") as f: | ||
return json.loads(f.read()) | ||
def fhir_resource(fhir_fixture) -> Dict: | ||
return json.loads(fhir_fixture) | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice - a fixture based on a fixture...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, just one comment on the test naming we might want to change. Nice advancement with the test case parameterization!
Signed-off-by: Dixon Whitmire <[email protected]>
This PR adds /ingress and /ingress/upload endpoints to connect. The "ingress" endpoints are used to handle all supported health protocols/formats including ASC X12, DICOM, FHIR, and HL7 (C-CDA is slated for a future release). The "ingress" provide a single integration point which removes the need for separate endpoints for each format.
Changes include:
I will create a new issue to support a configurable maximum request size for /ingress [POST]. The idea being that if a payload exceeds the size, clients would use /ingress/upload [POST] to upload the data message.
We will continue to store EDI message payloads within Kafka until #311 is implemented.
resolves #278 , #281 , #299