This PR addresses FHIR-42345 by applying more consistent styling across the specification. After discussion with the team, including review of the FHIR and US Core specifications, we determined that the following things should use code styling:
element paths, such as Patient.name.given and name.given
resource attributes, such as value[x]
symbols (when standing alone), such as $ and #
listed binding strengths, such as required, extensible, preferred, and example
flags, such as MU
slice names, such as bpSystolic and bpDiastolic
Author-defined FSH entity names, such as LateralityExtension
Aliases, such as $LOINC,
FSH codes, such as $LOINC#1234-5 and #active
Please review to ensure I've applied these consistently. Also consider if we should apply code styling to all of these, or if it is too much. Each type is applied in its own commit so we can more easily back out changes if needed.
This PR addresses FHIR-42345 by applying more consistent styling across the specification. After discussion with the team, including review of the FHIR and US Core specifications, we determined that the following things should use
code
styling:Patient.name.given
andname.given
value[x]
$
and#
required
,extensible
,preferred
, andexample
MU
bpSystolic
andbpDiastolic
LateralityExtension
$LOINC
,$LOINC#1234-5
and#active
Please review to ensure I've applied these consistently. Also consider if we should apply
code
styling to all of these, or if it is too much. Each type is applied in its own commit so we can more easily back out changes if needed.To see the autobuild of this branch, go here: https://build.fhir.org/ig/HL7/fhir-shorthand/branches/fsh-3.0-resolutions-cmm-4/index.html
NOTE: I did not apply these styles to the change log. I expect to do a full change log update in a separate commit.