Me/dpc 4324 hapi jpa eval

[MEspositoE14s]

🎫 Ticket

https://jira.cms.gov/browse/DPC-4324

Note:

This is strictly a proof of concept that will never be merged. It doesn't need to be reviewed fully, but if you choose to, don't let the large number of changes scare you off. The majority of them are deletes from removing dpc-attribution.

🛠 Changes

Completely removed dpc-attribution and replaced it with an off the shelf FHIR server.

ℹ️ Context

The ticket was to evaluate what FHIR services are currently available in the market and see if we could use them to improve our system. This PR shows the approximate level of effort required to completely remove dpc-attribution and replace it with an off the shelf FHIR server. This being a PoC, there are a number of caveats, though:

• I made as few configuration changes as possible on the FHIR server. We're essentially running the stock HAPI FHIR JPA server with no changes. In situations where dpc-attribution was adding non-standard FHIR functionality, I either moved that functionality to dpc-api or ignored it if it wasn't required to get our tests passing.
• A lot of the changes made were in our integration tests. We do some hackey stuff setting them up and tearing them down.
• I didn't write any new tests or port the end to end Postman tests.
• This PoC shouldn't be taken as an endorsement of this particular FHIR server, just the overall approach of replacing dpc-attribution with one. I only went with HAPI because it's completely free and already comes containerized.

Benefits to this approach

• We no longer have to maintain dpc-attribution. No more writing code to convert between FHIR objects and Hibernate entities.
• Instant R4 support.
• Instant paging support on the back end. Our existing PoC for paging on the front end should be fully functional with a few minor tweaks.
• Improved performance. Can bundle transactions together and handle batch submissions.
• Multitenancy if we decide to implement it.

Negatives

• While this particular FHIR server is free and open source, most aren't.
• This approach would require extensive testing to make sure that nothing changes from the customer's perspective, and if it does that it's for the better.
• Moving our existing data into the FHIR server will be a slog.

🧪 Validation

Run make ci-app locally and all of the tests should pass. You can also run the full api locally and fire queries at it with Postman.

[jdettmannnava]

Might as well remove dpc_attribution...

[MEspositoE14s]

Doh!