Does this field have a kinda “purpose” property like the FHIR CodeSystem.concept.designation.use?
Since I had misunderstood the initial proposed step, let me try again:
- Add an archetype annotation (to the AOM?) specifying that tools are to use the Description field instead of the element name for labelling a UI field. Would this annotation be set per archetype, per element, or perhaps per container?
- Implement support for this new annotation in relevant tools such as CKM, form builders and possibly form renderers
- Add workload for modellers to identify element names longer than some defined number of characters, make up a shortened version which is still unique, add the original question to the Description field, and potentially set the annotation mentioned above
- Get archetype reviewers to look at the Description when reviewing PROM archetypes, but the element names for all other archetypes
- Convince copyright holders that this is fine
And if I understand correctly, the alternative is:
- Slightly inconvenience PROM implementers who are using the natural language FLAT format paths
I don’t have a strong impression about the percentage of PROM questions which are longer than 50 characters. Perhaps people who have worked more actively with implementing PROM tools would know? I’ve had a quick look at the following archetypes. Some of them may not be PROMs, but they’re all standardised questionnaires intended to be filled out by the patient themselves. Numbers in brackets are the number of element and container names over 50 characters in length, and the total number of elements and containers.
- EPIC (32 of 70)
- MAP-hand (2 of 23)
- EQ-5D-5L (0 of 7)
- Birth Satisfaction Scale-Revised (0 of 14)
- Western Ontario and McMaster Universities Arthritis Index (0 of 28)
- Simplified Endoscopic Disease Severity Score for Crohn’s Disease (0 of 57)
- Short Inflammatory Bowel Disease Questionnaire (2 of 16)