TableDemo

Demo of table rendering issues for Firely

Issue with Text flow in right hand column

Wide Table

Element name Base Cardinality UK Core Cardinality Type Definition, Constraints and Notes Element name Base Cardinality UK Core Cardinality Type Definition, Constraints and Notes
id 0..1 1..1 id Logical id of this artifact.

In the UK Core the format is:

"UKCore-[BusinessNames]" (initial letters in upper case, no spaces between words).
id 0..1 1..1 id Logical id of this artifact.

In the UK Core the format is:

"UKCore-[BusinessNames]" (initial letters in upper case, no spaces between words).

Matrix table demo

Dataset New medicine Service Medication Review Appliance Use Review Vaccination Administration CPCS Emergency Supply CPCS Minor Illness Smoking Cessation Hypertension Case Finding CVD Contraception STT Palliative Hepatitis C
id 0..1 1..1 id Logical id of this artifact.

In the UK Core the format is:

"UKCore-[BusinessNames]" (initial letters in upper case, no spaces between words).
id 0..1 1..1 id Logical id of this artifact.

In the UK Core the format is:

"UKCore-[BusinessNames]" (initial letters in upper case, no spaces between words).

Long Table

Issue isn't happening here. Assume it's an issue with the css in the other IGs.

Element name Base Cardinality UK Core Cardinality Type Definition, Constraints and Notes
id 0..1 1..1 id Logical id of this artifact.

In the UK Core the format is:

"UKCore-[BusinessNames]" (initial letters in upper case, no spaces between words).
meta 0..1 0..1 Meta Metadata about the resource.

Not currently used in the UK Core.
- versionId 0..1 0..1 id Changes each time the content of the resource changes.

The version can be globally unique, or scoped by the Logical Id of the resource. Version identifiers are generally either a serially incrementing id scoped by the logical id, or a uuid, though neither of these approaches is required. There is no fixed order for version ids - clients cannot assume that a versionId that comes after another one either numerically or alphabetically represents a later version. The same versionId can never be used for more than one version of the same resource.

Not currently used in the UK Core.
- lastUpdated 0..1 0..1 instant If populated, this value changes each time the content of the resource changes. It can be used by a system or a human to judge the currency of the resource content.

Not currently used in the UK Core.
- source 0..1 0..1 uri A uri that identifies the source system of the resource.

Not currently used in the UK Core.
- profile 0..* 0..* canonical An assertion that the content conforms to a resource profile.

Not currently used in the UK Core.
- security 0..* 0..* Coding Security labels applied to this resource. These tags connect resources in specific ways to the overall security policy and infrastructure. Security tags can be updated when the resource changes, or whenever the security sub-system chooses to.

Not currently used in the UK Core.
- tag 0..* 0..* Coding Tags applied to this resource. Tags are used to relate resources to process and workflow. Applications are not required to consider the tags when interpreting the meaning of a resource.

Not currently used in the UK Core.
implicitRules 0..1 0..1 uri A set of rules under which this content was created.

Not currently used in the UK Core.
language 0..1 0..1 code Language of the resource content.

Not currently used in the UK Core.
text 0..1 0..1 Narrative Text summary of the resource, for human interpretation.

Not currently used in the UK Core.
contained 0..* 0..* Resource Contained, inline Resources.

Not currently used in the UK Core.
extension 0..* 0..* Extension Additional content defined by implementations.

See the ValueSetExtensions section for details of extensions that may be considered for use in UK Core value sets.
modifierExtension 0..* 0..* Extension Extensions that cannot be ignored.
url 0..1 1..1 uri Canonical identifier for this value set, represented as a URI (globally unique).

In the UK Core the format is:

"https://fhir.hl7.org.uk/ValueSet/UKCore-[BusinessNames]" (initial letters in upper case, no spaces between words).
identifier 0..* 0..* Identifier Additional identifier for the ValueSet, for example an OID.

If this is an OID, this should be in the following format:

    <identifier>
        <system value="urn:ietf:rfc:3986"/>
        <value value="urn:oid:2.16.840.1.113883.2.1.3.2.4.16.21"/>
    </identifier>


Further guidance may be needed in due course.
version 0..1 1..1 string Business version of the value set.

This will follow the Semantic Versioning standard [major.minor.patch].
name 0..1 1..1 string Computer readable name, this should reflect the name in the url element.

In the UK Core the format is:

"UKCore[BusinessNames]" (initial letters in upper case, no spaces between words).
title 0..1 1..1 string Human readable name, this should reflect the name in the url element.

In the UK Core the format is:

"UK Core [Business Names]" (initial letters in upper case, a space between each word).
status 1..1 1..1 code The publication status as defined in https://hl7.org/fhir/valueset-publication-status.html [draft | active | retired | unknown].

UK Core CodeSystems in development have a status of "draft".

UK Core CodeSystems that have been approved via Clinical and Technical Assurance have a status of "active".

UK Core CodeSystems that are no longer required in the UK Core have a status of "retired".
experimental 0..1 0..1 boolean Boolean value to indicate that this value set is authored for testing purposes and is not intended to be used for genuine usage.

Not currently used in the UK Core.
date 0..1 1..1 dateTime The date (and optionally time) when the value set was published or last changed. The date must change when the business version or status changes.

Just the date without time is populated in the UK Core.
publisher 0..1 1..1 string Name of the publisher (organization or individual).

For all UK Core value sets, where the base URL is https://fhir.hl7.org.uk, this will be "HL7 UK".
contact 0..* 1..* ContactDetail Contact details for the publisher.

See the template for details of how this must be populated for all UK Core value sets, where the base URL is https://fhir.hl7.org.uk/.
description 0..1 1..1 markdown A free text natural language description of the of the value set from a consumer's perspective. The textual description specifies the span of meanings for concepts to be included within the Value Set Expansion, and also may specify the intended use and limitations of the Value Set.

The general format should be as follows:

"A set of codes that define [description]".

In the UK Core there is a preference to use the words "define" or "describe" and more rarely, "identify".

For a value set containing a SNOMED CT Reference Set:

"A set of codes that describe [description]. Selected from the [RefSet display value] of the SNOMED CT UK coding system."

For a value set containing a SNOMED hierarchy:

"A set of codes that define [description]. Selected from the SNOMED CT UK coding system."

For a value set containing a complex set of SNOMED Reference Sets and/or hierarchies and/or individual concepts:

"A set of codes from the SNOMED CT UK coding system that: [description of RefSet/hierarchy1]; [description of RefSet/hierarchy2]; etc."

Where the value set includes nullFlavor(s) in addition to other sets of codes, for the nullFlavor section:

"Where no [MainCodeSystem(s)] coded information is available, a specific code from the nullFlavor CodeSystem can be used instead to indicate this."

For complicated descriptions, particularly where a complex set of SNOMED references is used, and where inclusion of a carriage return / line feed can make the content more presentable in Simplifier, the sequence can be inserted to start a new line and can be inserted to leave a line break before the next line starts.

See also the Example ValueSets from the UK Core section.
useContext 0..* 0..* UsageContext Context the content is intended to support. This is a code from extensible ValueSet https://hl7.org/fhir/valueset-usage-context-type.html, as well as a choice of CodeableConcept/Quantity/Range.

Not currently used in the UK Core.
jurisdiction 0..* 0..* CodeableConcept A legal or geographic region in which the code system is intended to be used (if applicable).

Not currently used in the UK Core but there may be a use case for derived assets.
immutable 0..1 0..1 boolean Indicates whether or not any change to the content logical definition may occur. If this is set to 'true', then no new versions of the content logical definition can be created. Normally immutability is set to 'false', which is the default assumption if it is not populated.

Not currently used in the UK Core.
purpose 0..1 0..1 markdown Explanation of why this value set is needed and why it has been designed as it has.

Not generally used in UK Core ValueSets but may have a use case in providing useful information not already evident from other content in a ValueSet.
copyright 0..1 1..1 markdown A copyright statement relating to the value set and/or its contents.

All UK Core ValueSets must contain the following:

"Copyright © [YYYY]+ HL7 UK Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. HL7® FHIR® standard Copyright © 2011+ HL7 The HL7® FHIR® standard is used under the FHIR license. You may obtain a copy of the FHIR license at https://www.hl7.org/fhir/license.html.", where [YYYY]=year of creation of the value set.

For UK Core ValueSets that contain SNOMED CT codes, the copyright statement must additionally include:

"This value set includes content from SNOMED CT, which is copyright © 2002+ International Health Terminology Standards Development Organisation (IHTSDO), and distributed by agreement between IHTSDO and HL7. Implementer use of SNOMED CT is not covered by this agreement.".

For UK Core ValueSets that contain dm+d codes, the copyright statement must additionally include:

"Copyright © NHS Digital"
compose 0..1 1..1 BackboneElement A set of criteria that define the contents of the value set by including or excluding codes selected from the specified code system(s) that the value set draws from. This is also known as the Content Logical Definition (CLD).

See the following sections for details on how to populate this:

- Content Logical Definition – ValueSets containing UK Core CodeSystems, and

- Content Logical Definition – ValueSets containing SNOMED concepts.
- lockedDate 0..1 0..1 date The Locked Date is the effective date that is used to determine the version of all referenced Code Systems and Value Set Definitions included in the compose that are not already tied to a specific version.

With a defined lockedDate the value set is considered "Locked". Otherwise, the value set may have different expansions as underlying code systems and/or value sets evolve. The interpretation of lockedDate is often dependent on the context - e.g. a SNOMED CT derived value set with a lockedDate will have a different expansion in USA than in UK. If a value set specifies a version for include and exclude statements, and also specifies a locked date, the specified versions need to be available that date, or the value set will not be usable.

Not currently used in the UK Core.
- inactive 0..1 0..1 boolean Whether inactive codes (codes that are not approved for current use) are in the value set.

If inactive = true, inactive codes are to be included in the expansion.

If inactive = false, the inactive codes will not be included in the expansion.

If absent, the behaviour is determined by the implementation, or by the applicable expansion parameters (but generally, inactive codes would be expected to be included).

Not currently used in the UK Core but a default value of "true" can be assumed.

Wide table