Example PROM-Archetypes
PROM | Description | Links |
|
|---|---|---|---|
EORTC QLQ C-30 View only: adl-file (editable):
| This archetype has been modeled according to the first style-guide-draft: it uses
| Paper-form: https://www.eortc.org/app/uploads/sites/2/2018/08/Specimen-QLQ-C30-English.pdf
Scoring-Manual: https://www.eortc.org/app/uploads/sites/2/2018/02/SCmanual.pdf |
|
SF-12v2 Health Survey View only: ADL file: please generate from the tool (as it may evolve!)
| This archetype follows my proposed modelling guide (as of 2024-12-23). @Koray Atalag | Paper form: not available publicly from QualityMetric (official LINK) but a sample from NHS is HERE. Scoring-Manual: not available publicly from QualityMetric (official LINK) but an online calculator is HERE. Original scoring paper (scanned copy): Ware, John E., Susan D. Keller, and Mark Kosinski. SF-12: How to score the SF-12 physical and mental health summary scales. Health Institute, New England Medical Center, 1995
|
|
MSKHQ Archetype proposal (International CKM) ADL-file:
| @Kanthan Theivendran | Versus Arthritis Musculoskeletal Health Questionnaire (MSK-HQ) |
|
Modeling details:
EORTC QLQ C-30 Screenshots
Short Form 12 version 2 (SF-12v2)
Paper form looks like this:
The instruction at the top applies to the whole questionnaire. To avoid using an empty Cluster to capture it one option could be to add this to ITEM_TREE. See I have renamed Item Tree as Overall Instructions and added the instruction into Description.
>>>>UPDATE 2024-12-23<<< I found ITEM_TREE under History has been renamed in Blood Pressure v2 archetype on CKM. So, I presume we could also use it to add content that relates to the overall Instrument.
Description has “@ internal @” notation - not sure about its semantics, though.
Also, note Oxford Hip Score in international CKM has question numbers attached to Item Level Descriptions - which I strongly suggest we do not append to actual questions. So, I’m proposing to represent Questionnaire, Group and Item level instructions in corresponding Description field and only include item full text in the Label.
Official Questionnaire: https://innovation.ox.ac.uk/wp-content/uploads/2014/09/FINAL_OHS_English_UK_SAMPLE-1.pdf
CKM Archetype looks like this. This is IMHO problematic (naturally as we do not yet have an agreed guide) due to:
Item labels do not faithfully represent original instrument (except if we decide to go with short labels)
Numbers should be associated with the Item level instructions and they should be faithful to original (actual syntax is “1. Item” instead of current “1 Item”)
Description has an arbitrary text: “Patient-reported extent of usual pain in hip during past 4 weeks.“ which is not in original instrument
Original full item text is given in Comment section: “Questionnaire wording: How would you describe the pain you usually had from your hip?“
I’m now tending towards this style (2024-12-23):
Item labels in short or long form (TBD). Include numbers and in correct format (e.g. 1. Blah) with the label ONLY if it’s given in the original instrument. If it’s in Instructions include as per below.
Original Instructions into corresponding Description sections:
Questionnaire level instructions into Description of Any event > data > ITEM_TREE.
Depending on whether we go with short or long labels we can also use that for label.Group level instructions into Description of CLUSTERs
Depending on whether we go with short or long labels we can also use that for label.Item level instructions into Description of ELEMENTs.
Naturally item labels will contain actual item text (long or short TBD)
In terms of short vs long labels - when you look at the mindmap it crops long text so not looking too bad IMHO:
Since the scores could be non integer numbers I chose QUANTITY data type without a unit (well sort of as it shows unit as “1“ ); see: https://openehr.atlassian.net/browse/SPECPR-13
I also used the following annotations (in line with some archetypes from Apperta Foundation such as EPIC):
Key: item_number | Value: 1,2,3 etc.
Key: variable_name | Value: GH1, PF2 etc.
Key: scale | Value: Physical Functioning (PF), Vitality (VT) etc.
Mini note on character case in annotations: keys in small case and values can be any (e.g. “Physical Functioning (PF)” - a tool or form renderer may use if for display so best to stick to its original definition or as commonly accepted). This is in line with some current (2024-12-23) Apperta archetypes.
….