Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Table of Contents

Outline

...

This page section explains the computational forms Computational Forms feature which can be used to calculate scores for specific attributes, based on the patient’s a Patient’s answers and a computational formula for the attribute. This feature also shows the dashboard user

Computational Forms provide the Dashboard User with a unique perspective on , including relative comparison of the scores across form submissions, each time the patient Patient submits the same form.

It is part of the Patient Reported Outcome Measures (PROMs) and is customisable to calculate scores for any required attribute, which can be used by researchers and clinicians Researchers or Clinicians to assist with clinical monitoring of a patientPatient's health journey.

Understanding Computations and adding them to .JSON content to create customisable Computational

...

Forms:

You can add Computations code and formula to a .JSON content similar to the ones below and use that to create computationsl formsComputational Forms.

View file
nameKOOS.json
View file
nameHOOS.json
View file
nameDASS-21.json

Note: Please check the bottom of the .JSON content attached above to see the Computations code and formula for KOOS, DASS-21, and HOOS respectively.

Example Computation Code for DASS-21 formForm

Code Block
  "computations": {
    "depression": {
      "display_name": "Depression",
      "display_order": 1,
      "type": "symbolic",
      "function": "q3 + q5 + q10 + q13 + q16 + q17 + q21",
      "improvement": "decrease"
    },
    "anxiety": {
      "display_name": "Anxiety",
      "display_order": 2,
      "type": "symbolic",
      "function": "q2 + q4 + q7 + q9 + q15 + q19 + q20",
      "improvement": "decrease"
    },
    "stress": {
      "display_name": "Stress",
      "display_order": 3,
      "type": "symbolic",
      "function": "q1 + q6 + q8 + q11 + q12 + q14 + q18",
      "improvement": "decrease"
    }
  }

...

  • "computations": { is the key that informs the system that there are computations to be done in this form.

  • "depression": indicates the attribute whose score will be calculated.

  • "display_name": "Depression" is the text that will be displayed to the patient on the app for this attribute.

  • "display_order": 1 indicates that the calculated score for the attribute ‘Depression’ will be displayed first among the three attributes on the score card. The dashboard user Dashboard User can just change the value from '1' here, to any other positive integer value to change the order in which the attributes are displayed on the score card in the form results of a patient, on Form Results in the dashboard. The order is displayed from left to right and top to bottom for more than three attributes as illustrated below - :

Depression ("display_order": 1)

Anxiety ("display_order": 2)

Stress ("display_order": 3)

"display_order": 4

"display_order": 5

"display_order": 6

"display_order": 7

"display_order": 8

"display_order": 9

  • "type": "symbolic" indicates the calculated score will be displayed as an integer value ('-ve', ‘0.0’, '+ve') on the dashboard.

  • "function": "q3 + q5 + q10 + q13 + q16 + q17 + q21" is the computational Computational formula for the attribute ‘Depression’ based on which the score will be calculated.

  • "improvement": "decrease" is used to visualize visualise the calculated score in ‘Green’ or ‘Red’ colour prefixed by an ‘Upward’ or ‘Downward’ arrow. This illustrates a relative comparison of the calculated score across form submissions.

    • In this case, if the calculated score decreases from the first form submission to the second, it will be shown in green with a downward green arrow in the second form submission. The opposite scenario, i.e., if the calculated scores increase from the first form submission to the second, it will be shown in red with an upward red arrow in the second form submission.

    • On the other hand, "improvement": "increase" can be used to achieve the opposite result. Here, if the calculated score decreases from the first form submission to the second, it will be shown in red with

    an
    • a downward red arrow in the second form submission. The opposite scenario, i.e., if the calculated scores increase from the first form submission to the second, it will be shown in green with an upward green arrow in the second form submission.

The same lines of code (2-7) can be repeated as shown in the picture above (repeated 3 times for the attributes - ‘Depression’, Anxiety' and ‘Stress) to calculate scores for various other attributes using the patient’s answers from the same form submission in ‘Form Results’. These scores can be viewed together on the dashboard under the ‘Scores’ card in 'Form Results’ as shown below.

...

Filter by label (Content by label)
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@3ffc84e
sortmodified
showSpacefalse
reversetrue
typepage
cqllabel = "kb-how-to-article" and type = "page" and space = "FPAKB"
labelskb-how-to-article

...