CARDS-1336: Serialize survey responses to EPIC-friendly json format

[veronikaslc]

POC for the CARDS-1336

To test with

• start with ./start_cards.sh -P prems -f mvn:io.uhndata.cards/cards-epic-integration/0.9-SNAPSHOT/slingosgifeature
• in the Questionnaire editor add ExternalLink to the questionnaire and some questions (label has to be epic)
• fill in the Questionnaire form and the create the corresponsing Visit form for it
• check the Questionnaire form link with URL suffix .toEpic.deep.json.
  For example: http://localhost:8080/Forms/84c7c113-4d7e-4b88-b890-4b20240abacf.toEpic.deep.json

In the generated JSON you should see:

{
  "resourceType": "QuestionnaireResponse",
  "questionnaire": "Questionnaire/<your created ExternalLink>",
  "status": "in-progress", // if Visit form is not submitted
  "subject": {
       "identifier": {
                "system": "<placeholder: CarePlan.activity.reference.type>",
                "value": "<placeholder: CarePlan.activity.reference.identifier.value -> CSN ID for an Appointment>"
            }
  },
  // for answers:
  [
      {
          "linkId": "<placeholder: ID of the Question ID Type>|<your created ExternalLink>",
          "text": "<question text>",
                  "answer": [
                      {
                           "valueString": "<question answer>"
                       }
                    ]
      }, 
  ]
}

[marta-]

This gives us a good start.

A general note:

• ideally we shouldn't have to specify .deep in the URL, as .toEpic should already produce an Epic-ready response (and the value-less json produced when .deep is omitted is not Epic-ready). Since the mechanism for achieving this is not yet present, we can report and implement it separately (see CARDS-1942) and update toEpic after this is implemented.

Things to do:

• anything dealing with data coming in and out of Epic, including this processor, should be placed in an epic specific core module (let's name it... epic-io? better names are welcome) so it can be reused across projects
• implement CARDS-1884 then revisit this code to actually output the Epic identifiers in the serialization.

[veronikaslc]

• Rebased on top of CARDS-1884 PR
• Integrated with CARDS-1884 to get the liked IDs to JSON

[marta-]

[ ] anything dealing with data coming in and out of Epic, including this processor, should be placed in an epic specific core module (let's name it... epic-io? better names are welcome) so it can be reused across projects

epic-integration (via @sdumitriu)

[veronikaslc]

Addressed all comments. Note that there are still some placeholders used like here or here

[sashaandjic]

---

QUESTION: I do not see "status": "in-progress", // if Visit form is not submitted as in:

[veronikaslc]

@sashaandjic Fixed the "status": "in-progress" part.

[veronikaslc]

Looking at the specs once again, it looks like the alternative status is completed.

[veronikaslc]

The placeholders left:

• CarePlan.activity.reference.type
• CarePlan.activity.reference.identifier.value
• ID of the Question ID Type

[veronikaslc]

Added build integration. Rebased on the latest dev.