Create sender transform to map zipcode to state(s) in UP
Closed this issue · 1 comments
chris-kuryak commented
Problem statement
There is a MARS requirement for OTC data (from MMTC, for example) to be able to route based on zipcode, instead of State. State is not a required field in the MARS spec, but zipcode is a required field.
What you need to know
- There are ~13 zipcodes that span multiple states. In that case, the solution needs to ensure that each state receives the message.
- Per Andrew W, solution should not enrich the message with a state, but rather still send the message without state information to the appropriate jurisdiction.
- Add transform that populate states in an extension
- Extension should be available to use in Jurisdictional Filter
Acceptance criteria
- Ability for OTC data in MARS format to be accepted without a state and be routed based on zipcode
- If zipcode spans multiple states, the message is routed to all applicable states
- If a message does not contain state information or the state field populated, the solution does not add state data to a message. Message is routed to appropriate jurisdiction without state information. ( Check with Chris)
- FHIR Path filter for the MARS topic is implemented that can route data based on this new extension that contains state information
- Tested with 10 zipcodes across 10 states to ensure functionality
chris-kuryak commented
Added new acceptance criteria based on demo of existing extension:
- FHIR Path filter for the MARS topic is implemented that can route data based on this new extension that contains state information
This will allow the message to be routed appropriately based on this new extension.