There is no jira specification file defined with the expected name of FHIR-tx-ecosystem in the xml folder of the https://github.com/HL7/Jira-Spec-Artifacts project. This must exist before ballot or publication.
The page skips a heading level: <h4> 'Scanning the Ecosystem' (id=scanning-the-ecosystem) follows <h2> 'Coordinating Server', so it should be <h3>. Heading levels must not skip a level going down (WCAG compliance test)HTML_HEADING_LEVEL_SKIPPED
en/requirements.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Most requirements apply to every server. Some apply only to a server that supports a particular code system or a particular feature, and those are stated conditionally - "if a server supports X, then it SHALL …". In the test cases these conditional requirements are gated by a mode: a test gated on a mode you do not pass to the runner does not run, and does not count as either a pass or a failure. So a server declares which of these sections apply to it by which modes it asks to be tested in. See Modes.'CONFORMANCE_STATEMENT_WORD
en/requirements.html
information
No conformance term found in the text: A code in a reserved code space is a valid code in the code system, whether or not anything in scope defines it.
When nothing does, its display is the code space's default display, which is a placeholder: another display is
not an error or a warningCONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.html
information
No conformance term found in the text: A global extension-codes supplement (marked with codesystem-supplement-global = true) is used for the code
system it supplements whether or not it is referenced, as if the code system defined its codes: its display is the
code's display, and a different display is an error (a warning with lenient-display-validation)CONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.html
information
No conformance term found in the text: An extension-codes supplement that is not global is only used when it is referenced. Its display is then the
code's display, but not the only correct one: a different display is a warningCONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.html
information
No conformance term found in the text: The codes an extension-codes supplement defines are only in an expansion when they are listed in the value set
(compose.include.concept), not when it includes all of the code systemCONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.html
information
No conformance term found in the text: A code in a reserved code space that a value set lists (compose.include.concept) is a member of it: it is in the
expansion, and $validate-code accepts it. A filter never selects a code in a reserved code space - not even a
concept in or code in filter that lists it - since such codes have no hierarchy or properties: it is not in the
expansion, $validate-code rejects it, and the filter does not make the expansion unclosedCONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.html
information
No conformance term found in the text: the latest version of that edition the server
hasCONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.html
information
No conformance term found in the text: that versionCONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.html
information
No conformance term found in the text: the edition and version the request asks for with
force-system-version, system-version or check-system-version, where it asks; otherwise the
server's default editionCONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.html
information
No conformance term found in the text: A concept matches when at least one of its active descriptions in the chosen language matches
the patternCONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.html
information
No conformance term found in the text: and the match is case-sensitiveCONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.html
information
No conformance term found in the text: Only one language is searchedCONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.html
information
No conformance term found in the text: the first language the request names - the
displayLanguage parameter, or if there is none, the HTTP Accept-Language header - that the
edition has descriptions in; if the request names none of the edition's languages, or no language
at all, the edition's default languageCONFORMANCE_STATEMENT_NOCONFWORD
en/requirements.html
information
The html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: 'CLASS SHALL be a string property whose value is the class name (e.g. PULM), in $lookup and in property filters. A server MAY also return the Part code for the class in $lookup, as a partCode part of the property (an informal extension)'CONFORMANCE_STATEMENT_WORD
When HL7 is publishing a resource, the publisher must be provided, and for WG 'fhir-pd' it should be 'HL7 International / FHIR Product Director'VALIDATION_HL7_PUBLISHER_MISSING
The nominated WG 'fhir-pd' means that the contact url should be 'http://www.hl7.org/Special/committees/fhirmg' but it was not foundVALIDATION_HL7_WG_URL
When HL7 is publishing a resource, the publisher must be provided, and for WG 'fhir-pd' it should be 'HL7 International / FHIR Product Director'VALIDATION_HL7_PUBLISHER_MISSING
The nominated WG 'fhir-pd' means that the contact url should be 'http://www.hl7.org/Special/committees/fhirmg' but it was not foundVALIDATION_HL7_WG_URL
The nominated WG 'fhir-pd' means that the publisher should be 'HL7 International / FHIR Product Director' but 'HL7 FHIR Product Director' was foundVALIDATION_HL7_PUBLISHER_MISMATCH
The nominated WG 'fhir-pd' means that the contact url should be 'http://www.hl7.org/Special/committees/fhirmg' but it was not foundVALIDATION_HL7_WG_URL