Implement the $ra.resolve-coding-gaps operation (replace existing)

[rob-reynolds]

Note: the spec has been updated. The spec takes precedence where it conflicts with these requirements.

As a Payer, I need the MeasureReport/$ra.resolve-coding-gaps operation implemented per the spec.

DESCRIPTION:

The Da Vinci Risk Adjustment IG (http://build.fhir.org/ig/HL7/davinci-ra/) has been updated to include the following stages:

• Report Generation
• Remediation
• Resolution

The $davinci-ra.resolve operation of the CQF Ruler (https://github.com/DBCG/cqf-ruler/blob/74fd64d830d3675c82b38bb587fe8469b7d98696/plugin/ra/src/main/java/org/opencds/cqf/ruler/ra/r4/ResolveProvider.java#L47) has been implemented, but it currently implements the functionality of the Remediation stage, not the Resolution stage.

The spec has been updated. The CQF Ruler needs to be updated correspondingly.

Preconditions:
The operation errors if the following precondition is violated:
for each group in the MR there is at most one ClinicalEvaluation DetectedIssue with a status of 'final'.

Changes:

• provide a new implementation of the $ra.resolve-coding-gaps operation

• The API is: https://build.fhir.org/ig/HL7/davinci-ra/OperationDefinition-ra.resolve-coding-gaps.html

• implement the following functionality:

For the subject, Measure Id parameters:

• Given a set of Risk Adjustment Coding Gap Document resource(s) (http://build.fhir.org/ig/HL7/davinci-ra/StructureDefinition-ra-coding-gap-bundle.html), the result of $ra.remediate-cc-gaps:

Request Type Mapping:

• closure-request => Evidence Status.closed-gap

• invalidation- => Evidence Status.invalid-gap

• creation-request =>

  • if a group already exists with that code, error, otherwise;
  • add a new group with the code
  • set Suspect Type = net-new
  • set Evidence Status = closed-gap

• for each most recent Clinical Evaluation DetectedIssue (http://build.fhir.org/ig/HL7/davinci-ra/StructureDefinition-ra-coding-gap-clinical-evaluation-detectedissue.html) entry in the bundle, of each coding gap

  • update the MeasureReport to the codingGapType using the Request Type Mapping.

Note: everything from the queried Coding Gap Document is retained, as is, except:

• new Bundle (document), with new id
• existing Composition gets status set to final
• existing MeasureReport.group(s) get updated
• existing MeasureReport.evaluatedResource(s) get updated

Note, the spec is currently a work in progress so where the information above conflicts with the spec, the information above takes precedence.

ACCEPTANCE CRITERIA:

• the operation is named MeasureReport/$ra.resolve-coding-gaps

• the API is:
  

• Given a the ThunderClient Risk Adjustment Collection.Resolve.Config requests have been posted, the corresponding $ra.resolve-coding-gaps request returns a valid Risk Adjustment Coding Gap Document, with an updated MeasureReport, and the Bundle and Composition are final

[rob-reynolds]

Pending Rob having a meeting with the RA leads.

[rob-reynolds]

Ready for implementation.

[rob-reynolds]

The work is done. Just need to get the following branch merged once the master branch (and this PR branch) are running: https://github.com/DBCG/cqf-ruler/tree/Branch_38c89957.

[rob-reynolds]

Completed. (superseded by #669 RA Approve operation implementation](#669)