SHALL

HL7 published implementation guides shall identify the ImplementationGuide.publisher as "HL7 International - <workgroup full name>" and ImplementationGuide.contact as the work group home page (i.e. http://www.hl7.org/Special/committees/[committee code])

Implementation Guides shall reference [canonical]/history.cfml as the source of information about other releases of the guide, and SHALL do at least from index.html (note: authoring the history.cfml page is not done by the IG; that's publishing infrastructur. it is built by cold fusion from the package-list.json file)

implementation guides shall present information to the user such that by default, nothing is hidden unless there are clearly defined tabs for changing views

implementation guides shall not contain any server side active content except that required by redirects for canonical URL management

it shall be possible to print pages from the IG for review/display

implementation guides shall include a downloadable version so people can host it locally, and it SHALL be referenced from the home page (potentially by a link to another page)

the IG must not refer to build.fhir.org at all

for HL7 IGs:

the realm in the canonical URL (http://hl7.org/fhir/[realm]/[code]/...) matches the specified jurisdiction in the IG resource (and uses the correct two letter abbreviation)

the realm in the ig resource matches the announced realm in the ballot

the package name (hl7.fhir.[realm].[code]) matches the realm and code in the canonical URL

the version is as agreed with the FHIR product director, and specified in fixed-business-version

information in the page header/footer must be consistent about realm, code, and version

the page footer must contain a copyright HL7 statement

implementation guides shall be designed to enable product/standard differentiation as described below

Note also these process requirements for submitting an IG for publishing by HL7:

the content must live in a github repository in the HL7 organization (or another TSC approved location)

the IG must build on the CI build, and must say which ballot/publication it is correctly in the page header and the

package-list.json (see FHIR IG PackageList doco) must exist in the repository, and have a correctly populated entry for the proposed release (except for date)

SHOULD

(nothing)

HL7 HTML Standards considerations

When HTML specifications are published on hl7.org, or fhir.org, the content of the pages is divided into 'product' and 'standard'.

Product

This is content that is under the ongoing control of the product manager, and the publication committee. The content
may be changed on an ongoing basis for the following reasons:
- new subsequent releases of the IG are published, and the status changes
- subsequent changes to web infrastructure require new links/styles/content
- external content changes require fixes to links / descriptions
- restyling decisions require syle updates

Release Header

Every HL7 implementation guide contains a release header on every page that contains status information about the release status of the IG as a whole:

This header is updated any time a new version of the IG is published - e.g. the old published versions of the IG are updated. In order to facilitate such actions, the IG - when presented for publication - SHALL have this HTML fragment in an appropriate place in the HTML source of the page:

<!--ReleaseHeader--><p id="publish-box">Publish Box goes here

<!--EndReleaseHeader-->

This must present in the product section of the page (see below) and must be rendered as a yellow box with a maroon border (as shown above).

Standard

This is controlled content; changes to this content are only ever made as formal technical corrections
with careful change control and announcements through HL7/FHIR Foundation formal channels. The only exception
to this is to correct external links that are not explicitly visible in the text of the IG.

Differentation

In order to make management simple, all HTML guides are split on the page into header, footer, and content.
The header and footer are 'product' and the content is 'standard', as shown on this diagram, where the shaded yellow is the content: