Logo

This specification conforms to FHIR®© R4

MedCom FHIR®© LandingPage

Styling the XHTML

As described in “2.4.0.4 Styling the XHTML” in FHIR R4 the XHTML fragment in the narrative MAY be styled in different ways, however, MedCom recommends the following, meaning that an implementer

This version of “2.4.0.4 Styling the XHTML” is intentionally only adjusted to point out the above recommendations and corrected the words MAY and SHOULD to follow the standard style of how MedCom’s Governance is expressed using upper case bold versions of MAY and SHOULD where needed.

MedCom has for this adjustment also narrowed down the example provided by HL7 FHIR. Click here to see the original HL7 FHIR example of XHTML styling. You can also find MedCom’s example. Click here to see MedCom’s example of XHTML styling.

MedCom will also for testing purposes provide example resources that includes all of these styles.

MedCom has no intention of explaining the further use of XHTML as the use of it SHOULD follow the general guidelines pointed out by the general HL7 FHIR specification of the actual version.

Using styling of text is recommended, but all systems SHALL be able to understand and display a linebreak, marked with <br/>.

xhtml-tag meaning xhtml-style
bold Bold Text { font-weight: bold }
italics Italics Text { font-style: italic }
underline Underlined Text { text-decoration: underline }
strikethrough Strikethrough Text { text-decoration: line-through }
left Left Aligned { text-align : left }
right Right Aligned { text-align : right }
center Center Aligned { text-align : center }
justify Justified { text-align : justify }
border-left Border on the left { border-left: 1px solid grey }
border-right Border on the right { border-right: 1px solid grey }
border-top Border on the top { border-top: 1px solid grey }
border-bottom Border on the bottom { border-bottom: 1px solid grey }
arabic List is ordered using Arabic numerals: 1, 2, 3 { list-style-type: decimal }
disc List bullets are simple solid discs { list-style-type: disc }
unlist List with no bullets { list-style-type: none }
xhtml-tag meaning xhtml-style
little-roman List is ordered using little Roman numerals: i, ii, iii { list-style-type: lower-roman }
big-roman List is ordered using big Roman numerals: I, II, III { list-style-type: upper-roman }
little-alpha List is ordered using little alpha characters: a, b, c { list-style-type: lower-alpha }
big-alpha List is ordered using big alpha characters: A, B, C { list-style-type: upper-alpha }
circle List bullets are hollow discs { list-style-type : circle }
square List bullets are solid squares { list-style-type: square }

Note: for testing purposes, there will be example resources that includes all of these styles. It is also available as XHTML and a standard stylesheet that includes all of these styles. Use of styles not on this list will require an arrangement between producing and consuming systems.

Authoring systems MAY refer to additional classes, but cannot rely on the fact that they will be supported. If the additional classes are critical for safe rendering, trading partner agreements will be required.

Authoring systems MAY also use internal styles using the style attribute. This has the advantage of not depending on external interpretation, but also has the side effect of making content more difficult to manage when rendering, so applications should use this approach with care.

Authoring systems MAY fix the following styling aspects of the content:

These style properties are specified in-line using the style attribute. Rendering systems SHOULD respect any of these rendering styles when they are specified in the style attribute, although appropriate interpretation is allowed in certain contexts (e.g. a low-contrast display for dark rooms or a high-contrast display for the visually impaired may adjust colors accordingly).

Note that rendering systems can ignore or override any of the internal or external styles described above, but SHOULD be careful to ensure that this is only done in the context of well-maintained trading partner agreements, as altering the presentation of the text may create clinical safety issues.

Authors MAY specify additional styles and style properties as specified in the CSS specification, but these are extensions to this specification and renderers are not required to heed them. It SHOULD be safe to view the narrative without these additional styling features available.

Note that there are additional rules around styling for documents presentation.



About

Support or contact

MedCom is responsible for this page. If you have any questions regarding this page, please contact fhir@medcom.dk or write to MedComs stream on Zulip.

Version of this documentation

The version of this documentation is Version 2.0.4. You can find the release note of the version here.



"FHIR® is the registered trademark of HL7 and is used with the permission of HL7. Use of the FHIR trademark does not constitute endorsement of this implementation guide by HL7, nor affirmation that this content is conformant to the various applicable standards"