You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to make some additions in the Trigger Code Reference building block to better suit our needs. We need to update the endpoint so rather than sending a list of codes to stamp, it automatically looks inside in the bundle for the reportable condition codes from the Reportability Response (RR), then stamps the eCR with those conditions.
Acceptance Criteria
In the endpoint:
The RR condition codes are extracted from the FHIR bundle
The TCR then stamps the bundle with each of those codes
The stamped bundle is returned in the response from the endpoint
It no longer needs/accepts a list of conditions sent it alongside the FHIR bundle
Unit tests for all functions
Testing
Yes, this ticket requires unit tests for new functions. No integration tests yet as that will come in in the next ticket.
Designs
No as this is entirely backend
Background & Context
The current stamping endpoint on the TCR isn't ideal for us as it requires us to pass in a list of conditions to the endpoint. We don't want to do this code gathering and passing in orchestration because it adds complexity and makes orchestration "too smart" when it should just be passing around bundles and calling endpoints. This change will let us do all the work in the TCR to keep orchestration simple.
The text was updated successfully, but these errors were encountered:
gordonfarrell
changed the title
Add new endpoint to the Trigger Code Reference service
Update endpoint to the Trigger Code Reference service
Jul 15, 2024
gordonfarrell
changed the title
Update endpoint to the Trigger Code Reference service
Update endpoint in the Trigger Code Reference service
Jul 15, 2024
Action Requested
We need to make some additions in the Trigger Code Reference building block to better suit our needs. We need to update the endpoint so rather than sending a list of codes to stamp, it automatically looks inside in the bundle for the reportable condition codes from the Reportability Response (RR), then stamps the eCR with those conditions.
Acceptance Criteria
In the endpoint:
Testing
Yes, this ticket requires unit tests for new functions. No integration tests yet as that will come in in the next ticket.
Designs
No as this is entirely backend
Background & Context
The current stamping endpoint on the TCR isn't ideal for us as it requires us to pass in a list of conditions to the endpoint. We don't want to do this code gathering and passing in orchestration because it adds complexity and makes orchestration "too smart" when it should just be passing around bundles and calling endpoints. This change will let us do all the work in the TCR to keep orchestration simple.
The text was updated successfully, but these errors were encountered: