Stream: conformance
Topic: Associating FHIRPath Expressions with Display labels
Simone Heckmann (Sep 06 2019 at 19:11):
We have been asked how to add German display labels to FHIR Profiles, and after bouncing a few ideas around (ElementDefinition.mapping, Translate-Extension on ElementDefinition.name, ElementDefinition.alias) we came to the conclusion that it would be much more useful to associate labels with FHIRPath expressions rather than elements to enable things like „Mobile Number“: Patient.telecom.where(use=‚mobile‘) etc.
Having such associations could then be used to support both the creation of Questionnaires with prepopulation/data extraction services as well as templates for narrative generation.
However, we are uncertain of how to represent these associations in FHIR. Could this be a CodeSystem with FHIRPath-Expressions as Codes and Labels as DisplayValues? ConceptMap? Something else?
Grahame Grieve (Sep 06 2019 at 21:04):
I'm not sure that I understand. You can provide code system supplements that contain german display equivalents for the codes - that looks like your use case above. Or you can use the translation extension to put alternate displays on elements.
What you've asked feels like you're trying to put displays on things that don't have displays?
Lloyd McKenzie (Sep 06 2019 at 21:36):
If you're wanting to give specific labels to particular paths into elements, that's starting to tread into the place of Questionnaire - where you're creating a distinct data model for display that exposes resource elements in a different way than they're naturally represented within the resources.
Simone Heckmann (Sep 07 2019 at 11:31):
@Grahame Grieve we're not looking at translating codes but at creating shareable translations for FHIR element names, like "birthDate" -> "Geburtsdatum".
We have been thinking about SDC-Questionnaires, but I thought the same kind of translations could be useful to generate Narrative templates. I am thinking about having a common structure that maps Element paths to display labels as a source to generate both the Questionnaire for data capture as well as the Narrative for presentation...
Simone Heckmann (Sep 07 2019 at 11:35):
As another example, date values would be presented differntly in a German UI ("02.09.1980" instead of "1980-09-02")
I couldn't represent that by just adding a translation to the element , but I could do it with a FHIRPath-Expression...
Simone Heckmann (Sep 07 2019 at 11:43):
I suppose a SDC-Questionnaire with FHIRPath expressions to prepopulate the items could in fact double as a Narrative template... It's just a different way of rendering it.
It's just that a Questionnaire seems a bit of an obscure way to maintain the translations...But with the ongoing discussions about creating reuseable parts for Questionnaires, i guess, why not...?
Lloyd McKenzie (Sep 07 2019 at 14:12):
I'd encourage not changing the date format for presentation. While yyyy-mm-dd isn't the typical format used in either Europe or North America, it's unambiguous and understood in both places.
Grahame Grieve (Sep 07 2019 at 21:01):
creating shareable translations for FHIR element names
The IG tooling expects that you'll do that using the http://hl7.org/fhir/StructureDefinition/translation extension
Alexander Kiel (Sep 11 2019 at 08:37):
As another example, date values would be presented differntly in a German UI ("02.09.1980" instead of "1980-09-02")
I couldn't represent that by just adding a translation to the element , but I could do it with a FHIRPath-Expression...
For Dates I would also say that the UI can present them in the appropriate format without the need to do anything in FHIR. Knowning the machine readable date plus the language is sufficient to display any date or datetime.
Lloyd McKenzie (Sep 11 2019 at 12:37):
That's true for the computable data, not for the transmitted narrative. However, the narrative could theoretically be seen by people in any country, so unambiguous is best.
Last updated: Apr 12 2022 at 19:14 UTC
