Stream: implementers
Topic: GF#16525 making the Standard Extensions more visible
Eric Haas (Mar 25 2019 at 21:19):
We have been discussing options on how make the reader of the specification more aware of the standard extensions defined for each FHIR resource. here are some options I mocked up to help us decide which approach is most appropriate. We are seeking feedback on which option seems best.
Eric Haas (Mar 25 2019 at 21:20):
Option 1 keep as is:
find-extension-option1.png
Eric Haas (Mar 25 2019 at 21:21):
Option 2 add link to extension below content view:
find-extension-option2.png
Eric Haas (Mar 25 2019 at 21:22):
Option 3 add table of extensions to content page:
find-extension-option3.png
Yunwei Wang (Mar 26 2019 at 13:14):
I like Option 3 but I am afraid the list would be too long. Also do you include the extensions applied to data type? For example, for Patient resource, do you also list extensions for Address data type?
Lloyd McKenzie (Mar 26 2019 at 15:04):
The list could be quite long. It also gives almost equal prominence to the extensions as it does to the core elements. The whole point of something being an extension is that they're less prominent and don't distract implementers from the main spec.
Last updated: Apr 12 2022 at 19:14 UTC
