Ability to evaluate filters from a specified Receiver Settings
Closed this issue · 1 comments
chris-kuryak commented
Problem statement
We need the ability to evaluate filters from a specified receiver while using the ./prime fhirdata command. We need to be able to determine wether the FHIR path filter is invalid and if any exceptions are thrown while they are evaluated.
What you need to know
There's a separate ticket to evaluate the conditionFilter and remove the conditions. We should be able to leverage existing logic for evaluating the receiver filters to return whether a filters is passing or failing. Keep in mind that whatever gets printed while running the CLI command will need to be returned in an API response in a follow up ticket.
- CLI Command: ./prime fhirdata
- ...
Acceptance criteria
- Status of filters is returned in the CLI response
JessicaWNava commented
Notes for myself:
- Should evaluate jurisdictionalFilter, qualityFilter, routingFilter, processingModeFilter, conditionFilter, mappedConditionFilter. Skipping reverseTheQualityFilter because that is no longer supported in the UP
- If it fails qualityFilter, jurisdictionalFilter, routingFilter, processingModeFilter we shouldn't return the message.
- When evaluating the conditionFilter or mappedConditionFilter we only need return which Observations got filtered out or if there are exceptions with the filter (Logic to actually remove not a part of this ticket though.)
- Only occurs when a receiver is specified.
- Should occur before applying any transforms and after stamping the bundle with condition codes.