jimfuqian/BB2-3679-Expose-PACA-data-Claim-and-ClaimResponse-thru-BB2-API

[JFU-NAVA-PBC]

JIRA Ticket:
BB2-3679

As a BB2 Team member, I want to familiarize the team with PAC data, so that we can make a decision going forward on the LOE for including this data in the API for end users.

What Does This PR Do?

A POC prototype that expose PACA data: Claim, ClaimResponse on BB2 API:

GET Claim by claim ID
POST based search Claim given mbi etc.

GET ClaimResponse by claim ID
POST based search ClaimResponse given mbi etc.

What Should Reviewers Watch For?

Check out the PR and spin up a local BB2 as instructed by README

Try to call the PACA data end points through:

Swagger UI
TestClient

Note,

1. There is migration on crosswalk adding user_mbi as column
2. Use 'Gold bene' (BBUser10000) in auth flow, it has Claim and ClaimResponse data.

If you're reviewing this PR, please check for these things in particular:

Validation

the POC prototype can be played using testclient and swagger UI:

1. Checkout PR

2. Spin up a local BB2

3. Point browser to http://localhost:8000/testclient, and authorize using Gold bene (BBUser10000)

4. After auth completed, click FHIR endpoints: Claim and ClaimResponse as shown below:

5. 

6. Should get paginated results:

7. Claims Search (73 total):

8. 

9. ClaimResponse Search (73 total):

10. 

11. Swagger UI: Complete Swagger UI authorize as instructed by description on the swagger UI page (note, need to customized openapi.yaml before kick off docker, substitute all sandbox URL base to http://localhost:8000), also need to register your app e.g. MyApp

12. Claim Search:

13. Claim Search Response:
    

14. Claim GET (pick a claim ID from the search result bundle, e.g.):
    

15. Do similar GET and Search for ClaimResponse....

What Security Implications Does This PR Have?

Please indicate if this PR does any of the following:

• Adds any new software dependencies
• Modifies any security controls
• Adds new transmission or storage of data
• Any other changes that could possibly affect security?

• Yes, one or more of the above security implications apply. This PR must not be merged without the ISSO or team
  security engineer's approval.

Any Migrations?

• Yes, there are migrations
  • The migrations should be run PRIOR to the code being deployed
  • The migrations should be run AFTER the code is deployed
  • There is a more complicated migration plan (downtime,
    etc)
• No migrations

What Security Implications Does This PR Have?

Please indicate if this PR does any of the following:

• Adds any new software dependencies
• Modifies any security controls
• Adds new transmission or storage of data
• Any other changes that could possibly affect security?

• Yes, one or more of the above security implications apply. This PR must not be merged without the ISSO or team
  security engineer's approval.

Any Migrations?

• Yes, there are migrations
  • The migrations should be run PRIOR to the code being deployed
  • The migrations should be run AFTER the code is deployed
  • There is a more complicated migration plan (downtime,
    etc)
• No migrations