FHIR Terminology Ecosystem IG
1.11.1-snapshot - Release International flag

FHIR Terminology Ecosystem IG, published by HL7 FHIR Product Director. This guide is not an authorized publication; it is the continuous build for version 1.11.1-snapshot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/fhir-tx-ecosystem-ig/ and changes regularly. See the Directory of published versions

Test Case Registry

Modes

Summary of the impact of the modes. The tests in the general mode are run by default; the tests in the other modes are only run when the mode is passed to the runner:

Mode Suites (test count) Tests
general (all the suites that are not marked with another mode) 828
tx.fhir.org extension-codes-3166 (6)
tx.fhir.org (20)
UCUM (21)
compare (28)
bugs (28)
related2 (33)
langcodes (43)
ecosystem (12)
simple-cases (3 of 52)
loinc (14 of 126)
208
loinc loinc (126)
126
snomed snomed (127)
sct-ec (13)
sct-ecl (233)
373
omop omop (27)
27
mimetypes mimetypes (39)
39
icd-11 icd-11 (132)
132
icf icf (70)
icf-ec (13)
83
Total 47 suites 1802

Suites

The flags say when a suite runs: its mode (only when that mode is passed to the runner), the features the server must declare, the FHIR version, and whether its tests must run in order. Disabled suites are struck out.

Name Flags Description
metadata

tests for minimal requirements for metadata statements

properties general

Testing the ValueSet.compose.property element

simple-cases general

basic tests, setting up for the API tests to come

parameters general

Testing out the various expansion parameters that the IG publisher makes use of

language general

Testing returning language by request, getting the right designation

language2 general

A series of tests that test display name validation for various permutations of languages

global-lang-pack general

Global language packs: a language pack (codesystem-supplement-type = lang-pack) marked with codesystem-supplement-global = true is used for the code system it supplements whether or not it is referenced; any other supplement is only used when it is referenced

extension-codes general

Extension-codes supplements: a code system reserves a code space (codesystem-reservedCodeSpace) for users to define their own codes, and a CodeSystem supplement of type extension-codes defines codes in it, with displays. A global one (codesystem-supplement-global) is used whether or not it is referenced, as if the code system defined the codes; one that is not global is only used when it is referenced. A code in the reserved code space that nothing in scope defines is valid, with the code space's default display (default-display, or User-assigned). In a value set, a reserved code is a member of an include of all of the code system (so its expansion is unclosed) and of an include that lists it; a filter never selects one

extension-codes-3166 tx.fhir.org

Extension-codes supplements for ISO 3166, whose user-assigned codes are its reserved code space. In the tx.fhir.org mode, since no general suite tests ISO 3166

extensions general

Testing proper handling of extensions, which depends on the extension

validation general

Testing various validation parameter combinations

version general

Testing various version issues. There's two versions of a code system, and three value sets that select different versions

overload general

A set of tests that test out handling of value sets that cross versions of the same code system

fragment general

Testing handling a code system fragment

big general

Testing handling a big code system

other general

Misc tests based on issues submitted by users

errors general

Testing Various Error Conditions

deprecated general

Testing Deprecated+Withdrawn warnings

notSelectable general

Testing notSelectable

inactive general

Testing Inactive codes

case general

Test Case Sensitivity handling

translate general

Tests for ConceptMap.$translate

translate2 general

Tests for ConceptMap.$translate

tho general

Misc assorted test cases from tho

exclude general

Tests for proper functioning of exclude

search general

Tests for proper functioning of text search. Note what we're not interested in the implementation of the text search itself, so we only test very obvious results. We're just interested in testing support for the parameter

default-valueset-version general

Test the default-valueset-version parameter

tx.fhir.org tx.fhir.org

These are tx.fhir.org specific tests. There's no expectation that other servers will pass these tests, and they are not executed by default. (other servers can, but they depend on other set up not controlled by the tests

loinc loinc

LOINC tests. These depend on the LOINC release (2.83) and the accessory files the server has loaded, and every request names version 2.83

snomed snomed

This snomed tests are based on the testing subset in the tx-ecosystem IG github repo (see /tx-source)

sct-ec snomed

Extension-codes supplements for the SNOMED CT test edition: a supplement gives some post-coordinated expressions human displays. In the snomed mode, and a suite of its own, since its global supplement would change the snomed suite's other tests

sct-ecl snomed

SNOMED CT ECL tests (expand + validate-code), split out of the snomed suite for manageability. Files live in sct/ecl/.

batch general

Test Batch Validation

omop omop

Tests for OMOP implementations. Note that some servers only do OMOP (and some don't). The tests are based on a stable subset of OMOP maintained by Davera Gabriel

UCUM tx.fhir.org

UCUM Test Cases

mimetypes mimetypes

Tests for the mime types code system (BCP 13). Type and subtype have no hierarchy, but parameters narrow a media type, and the base filter selects by type or type/subtype

compare tx.fhir.org

Tests for candidate new 'related' operation

bugs tx.fhir.org

A series of tests that deal with discovered bugs in FHIRsmith. These tests are specific to FHIRsmith - internal QA

permutations general

A set of permutations generated by Claude with the goal of increasing test coverage.

icd-11 icd-11

ICD-11 Test Cases. See tests/icd-11/doco.txt for what these assert and why several of them are expected to fail against the current ICD-API.

regex-bad general

Bad Regex - checking defences against denial of service attack. These are unusual because servers have the option to succeed, or to refuse the request

related2 tx.fhir.org

Tests for $compare operation - comparing two value sets to determine their relationship (equivalent, subset, superset, overlap, disjoint, unknown)

langcodes tx.fhir.org

IETF language code (BCP-47) test cases

ecosystem tx.fhir.org

Value sets whose code systems are spread across more than one server in the ecosystem, so that no single server holds them all: tx.fhir.org answers for them by asking the other servers

closure feature: closure sequential

$closure: build a closure table one concept at a time. The tests depend on each other, so the suite runs in order, on one thread, after all the other suites. The table is reset by the first test, and the code system it uses is only sent in that request

icf icf

Tests for ICF (2001a) qualifiers: the .XYZ grammar (extent, nature, localization; 8 = not specified), the displays it generates, enumerated value sets with qualified codes, and value set filters that require or forbid qualifiers

icf-ec icf

Extension-codes supplements for ICF (2001a), whose qualified (post-coordinated) codes are a grammar: a supplement gives some of them human displays. In the icf mode, and a suite of its own, since its global supplement would change the icf suite's other tests

Tests

Name Operation Flags Description
metadata

tests for minimal requirements for metadata statements

metadata $metadata

Check that the minimum expected things are found in the server CapabilityStatement

term-caps $term-caps

Check that the minimum expected things are found in the server TerminologyCapabilities

properties general

Testing the ValueSet.compose.property element

expand-with-valueset.compose.property-all-properties-wildcard $expand

Expand a value set defined to request all properties using ValueSet.compose.property with a wildcard character

expand-with-valueset.compose.property-all-properties-enums $expand

Expand a value set defined to request all properties using ValueSet.compose.property with enumerated properties

simple-cases general

basic tests, setting up for the API tests to come

simple-expand-all $expand

Expansion containing all the code system

simple-expand-active $expand

Expansion containing only the active codes in the code system

simple-expand-inactive $expand

Expansion containing only the inactive codes in the code system

simple-expand-enum $expand

Expansion containing an enumerated set of codes in the code system

simple-expand-enum-bad $expand

Expansion containing an enumerated set of codes in the code system, including an invalid code. The server may refuse to expand the value set (4xx), or expand it without the invalid code, saying so in an expansion-issue (200)

simple-expand-enum-invalid $expand

Expansion of a value set that enumerates a valid code and an invalid one ('xxxx'). The server may refuse to expand the value set (4xx), or expand it with just the valid code, saying the include referred to an invalid code in an expansion-issue (200)

simple-expand-isa-invalid $expand

Expansion of a value set that includes a valid code, and everything that is-a xxxx (a code that is not in the code system). The server may refuse to expand the value set (4xx), or expand it with just the valid code, saying the filter referred to an invalid code in an expansion-issue (200)

simple-validate-enum-invalid $validate-code

$validate-code of an unknown code (yyyy) against a value set that is invalid: it lists a code that is not in the code system (xxxx). Not valid, and as well as the usual errors, an error saying that the value set is not valid, and why

simple-validate-isa-invalid $validate-code

$validate-code of an unknown code (yyyy) against a value set that is invalid: it has an is-a filter on a code that is not in the code system (xxxx). Not valid, and as well as the usual errors, an error saying that the value set is not valid, and why

simple-expand-isa $expand

Expansion containing a filter on the code system using is-a relationship

simple-expand-child-of $expand

Expansion containing a filter on the code system using child-of relationship. This is testing R5/R4 transformation

simple-expand-concept-not-in $expand

Expansion with a concept not-in filter: every code except the listed ones. A child of a listed code (code2aI, code2aII) is still in: not-in excludes only the codes it lists

simple-expand-code-not-in $expand

The same, with the filter on the code property

simple-expand-isa-o2 $expand tx.fhir.org

Expansion containing a filter on the code system using is-a relationship with paging (tx.fhir.org internal test)

simple-expand-isa-c2 $expand tx.fhir.org

Expansion containing a filter on the code system using is-a relationship with paging (tx.fhir.org internal test)

simple-expand-isa-o2c2 $expand tx.fhir.org

Expansion containing a filter on the code system using is-a relationship with paging (tx.fhir.org internal test)

simple-expand-prop $expand

Expansion containing a filter on the code system using a property value

simple-expand-repeating-prop $expand

A concept may carry several values for one property (CodeSystem.concept.property is 0..*). code3 has dup=alpha and dup=beta; filtering on beta - which is not its first value - must still select it

simple-expand-repeating-prop-values $expand

expansion.contains.property is 0..* as well: a concept carrying several values for one property must report all of them, not just one

simple-expand-regex $expand

Expansion containing a filter on the code system using regex on the codes

simple-expand-regex-alt $expand

A regex filter matches the whole code: code2|code3 selects code2 and code3, and not the codes that start with code2 (it is ^(?:code2|code3)$, not ^code2|code3$)

simple-expand-regex2 $expand

Expansion containing a filter on the code system using regex on the codes using a regex known to cause a problem on at least one server

simple-expand-regexp-prop $expand

Expansion containing a filter on the code system using regex on the property values of prop

simple-expand-regex-none $expand

Expansion containing a filter on the code system using a valid regex on the codes that matches none of them. The expansion is empty - an include whose filter selects nothing must not be treated as an include with no filter, which would select every code in the code system

simple-lookup-1 $lookup

Check that $lookup works (there's not many tests for $lookup because it's not used much by the tools)

simple-lookup-2 $lookup

Check that $lookup works (there's not many tests for $lookup because it's not used much by the tools)

simple-lookup-zxx $lookup

$lookup with a valid displayLanguage that the code system has no content in (zxx, No linguistic content): the display is in the default language, and a warning says so

simple-lookup-unknown-property $lookup

$lookup asking for a property the code system defines (prop) and one the server does not know (x-unknown-property): the server ignores the property it does not know - no error or warning - and returns the one it does

simple-lookup-only-unknown-property $lookup

$lookup asking only for a property the server does not know: it is ignored, and no properties are returned

simple-expand-unknown-property $expand

$expand asking for a known property and one the server does not know: the unknown property is ignored - it is not declared in expansion.property, and there is no error or warning

simple-expand-all-count $expand

Expansion containing all the code system, but only a count

simple-expand-contained $expand

Expansion where the compose refers to a contained value set

simple-expand-contained-nested $expand

Expansion where the compose refers to a contained value set, which itself refers to another contained value set (a #id is resolved against the container's contained resources)

simple-expand-contained-circular $expand

Expansion where two contained value sets import each other: a circular reference, which is an error

simple-subsumes-parent $subsumes

A code subsumes a code nested inside it

simple-subsumes-child $subsumes

the mirror of simple-subsumes-parent

simple-subsumes-equivalent $subsumes

A code is equivalent to itself

simple-subsumes-transitive $subsumes

Subsumption follows the whole nesting, not just direct children

simple-subsumes-siblings $subsumes

Two sibling codes do not subsume each other

simple-subsumes-unrelated $subsumes

Two root level codes do not subsume each other

simple-subsumes-root $subsumes

A root code does not subsume a code under a different root

simple-subsumes-unknown-code $subsumes

codeA is not in the code system

simple-subsumes-parent-coding $subsumes

As simple-subsumes-parent, but with codingA/codingB

simple-subsumes-child-coding $subsumes

As simple-subsumes-child, but with codingA/codingB

simple-subsumes-equivalent-coding $subsumes

As simple-subsumes-equivalent, but with codingA/codingB

simple-subsumes-transitive-coding $subsumes

As simple-subsumes-transitive, but with codingA/codingB

simple-subsumes-siblings-coding $subsumes

As simple-subsumes-siblings, but with codingA/codingB

simple-subsumes-unrelated-coding $subsumes

As simple-subsumes-unrelated, but with codingA/codingB

simple-subsumes-root-coding $subsumes

As simple-subsumes-root, but with codingA/codingB

simple-subsumes-unknown-code-coding $subsumes

As simple-subsumes-unknown-code, but with codingA/codingB

simple-subsumes-no-system $subsumes

codeA and codeB with no system parameter - the request is invalid (400)

simple-subsumes-no-system-coding $subsumes

As simple-subsumes-no-system, but with codingA/codingB that have no system

parameters general

Testing out the various expansion parameters that the IG publisher makes use of

parameters-expand-all-hierarchy $expand

Expand an entire code system, and check that the code system replicates the hierarchy. Note that for all the hierarchical expansions, the flag 'flat' means that the server is not expected to provide a hierarchical expansion

parameters-expand-enum-hierarchy $expand

Expand an enumerated value set - no hierarchy in this case

parameters-expand-isa-hierarchy $expand

Expand an is-a value set, and preserve the hierarchy

parameters-expand-all-active $expand

expand all the active codes - hierarchy is preserved

parameters-expand-active-active $expand

Expand all the active codes, and specify active codes in a parameter

parameters-expand-inactive-active $expand

Expand all the codes, including inactive ones, but specify active codes only in a parameter

parameters-expand-enum-active $expand

Expand an enumerated value set, with active codes only in a parameter

parameters-expand-isa-active $expand

Expand an is-a value set, only the active codes

parameters-expand-all-inactive $expand

expand all the active codes, including inactive codes - hierarchy is preserved

parameters-expand-active-inactive $expand

to be provided

parameters-expand-inactive-inactive $expand

to be provided

parameters-expand-enum-inactive $expand

to be provided

parameters-expand-isa-inactive $expand

to be provided

parameters-expand-all-designations $expand

to be provided

parameters-expand-enum-designations $expand

to be provided

parameters-expand-isa-designations $expand

to be provided

parameters-expand-all-definitions $expand

to be provided

parameters-expand-enum-definitions $expand

to be provided

parameters-expand-isa-definitions $expand

to be provided

parameters-expand-all-definitions2 $expand

to be provided

parameters-expand-enum-definitions2 $expand

to be provided

parameters-expand-enum-definitions3 $expand

specifically to test out http://hl7.org/fhir/StructureDefinition/valueset-concept-definition

parameters-expand-isa-definitions2 $expand

to be provided

parameters-expand-all-property $expand

to be provided

parameters-expand-enum-property $expand

to be provided

parameters-expand-isa-property $expand

to be provided

parameters-expand-supplement-none $expand

Base line for supplement tests

parameters-expand-supplement-good $expand

Make sure the useSupplement parameter works

parameters-expand-supplement-bad $expand

Make sure the useSupplement parameter fails when it's not valid

parameters-validate-supplement-none $validate-code

Base line for supplement tests - validation

parameters-validate-supplement-good $validate-code

Make sure the useSupplement parameter works for validation

parameters-validate-supplement-bad $validate-code

Make sure the useSupplement parameter fails when it's not valid - for validation

parameters-lookup-supplement-none $lookup

Base line for supplement tests - validation

parameters-lookup-supplement-good $lookup

Make sure the useSupplement parameter works for lookup

parameters-lookup-supplement-bad $lookup

Make sure the useSupplement parameter fails when it's not valid - for lookup

language general

Testing returning language by request, getting the right designation


see languages.md for an explanation
language-echo-en-none $expand

to be provided

language-echo-de-none $expand

to be provided

language-echo-en-multi-none $expand

to be provided

language-echo-de-multi-none $expand

to be provided

language-echo-en-en-param $expand

to be provided

language-echo-en-en-vs $expand

to be provided

language-echo-en-en-header $expand

to be provided

language-echo-en-en-vslang $expand

to be provided

language-echo-en-en-mixed $expand

to be provided

language-echo-de-de-param $expand

to be provided

language-echo-de-de-vs $expand

to be provided

language-echo-de-de-header $expand

to be provided

language-echo-en-multi-en-param $expand

to be provided

language-echo-en-multi-en-vs $expand

to be provided

language-echo-en-multi-en-header $expand

to be provided

language-echo-de-multi-de-param $expand

to be provided

language-echo-de-multi-de-vs $expand

to be provided

language-echo-de-multi-de-header $expand

to be provided

language-xform-en-multi-de-soft $expand

to be provided

language-xform-en-multi-de-hard $expand

to be provided

language-xform-en-multi-de-default $expand

to be provided

language-xform-de-multi-en-soft $expand

to be provided

language-xform-de-multi-en-hard $expand

to be provided

language-xform-de-multi-en-default $expand

to be provided

language-echo-en-designation $expand

to be provided

language-echo-en-designation-bare $expand

The designation parameter is a token: a bare code (no system) matches a designation's language, or its use code from any system. designation=es is the same as urn:ietf:bcp:47|es. A language matches exactly here: de-CH, not de

language-echo-en-designations $expand

to be provided

language2 general

A series of tests that test display name validation for various permutations of languages


see display/index.md for an explanation
validation-right-de-en $validate-code

to be provided

validation-right-de-ende-N $validate-code

to be provided

validation-right-de-ende $validate-code

to be provided

validation-right-de-none $validate-code

to be provided

validation-right-en-en $validate-code

to be provided

validation-right-en-ende-N $validate-code

to be provided

validation-right-en-ende $validate-code

to be provided

validation-right-en-none $validate-code

to be provided

validation-right-none-en $validate-code

to be provided

validation-right-none-ende-N $validate-code

to be provided

validation-right-none-ende $validate-code

to be provided

validation-right-none-none $validate-code

to be provided

validation-wrong-de-en $validate-code

to be provided

validation-wrong-de-en-bad $validate-code

Same request, but with an invalid displayName parameter

validation-wrong-de-ende-N $validate-code

to be provided

validation-wrong-de-ende $validate-code

to be provided

validation-wrong-de-none $validate-code

to be provided

validation-wrong-en-en $validate-code

to be provided

validation-wrong-en-ende-N $validate-code

to be provided

validation-wrong-en-ende $validate-code

to be provided

validation-wrong-en-none $validate-code

to be provided

validation-wrong-none-en $validate-code

to be provided

validation-wrong-none-ende-N $validate-code

to be provided

validation-wrong-none-ende $validate-code

to be provided

validation-wrong-none-none $validate-code

to be provided

global-lang-pack general

Global language packs: a language pack (codesystem-supplement-type = lang-pack) marked with codesystem-supplement-global = true is used for the code system it supplements whether or not it is referenced; any other supplement is only used when it is referenced

glp-cs-validate-de $cs-validate-code

An unreferenced global language pack is used: the German display it defines for the code is valid when German is asked for

glp-validate-de $validate-code

The same in a value set: the global language pack for the code system is used without the value set or the request referring to it

glp-validate-nl-unreferenced $validate-code

A language pack that is not global (lang-pack, without codesystem-supplement-global) is not used unless it is referenced, even though it was passed in tx-resource: its Dutch display is not valid

glp-validate-nl-referenced $validate-code

Once the same supplement is referenced with useSupplement, its Dutch display is valid

glp-cs-validate-nl-unreferenced $cs-validate-code

The same against the code system: a language pack that is not global is not used unless it is referenced, so its Dutch display is not valid

glp-cs-validate-nl-referenced $cs-validate-code

Once referenced with useSupplement, a supplement passed in tx-resource is used by CodeSystem $validate-code too

glp-lookup-de $lookup

$lookup in German: the display and the German designation come from the unreferenced global language pack, which is reported as a used-supplement

glp-lookup-nl-unreferenced $lookup

$lookup in Dutch: a language pack that is not global (lang-pack, without codesystem-supplement-global) is not used unless it is referenced, so there is no Dutch display or designation, and it is not a used-supplement. The German global language pack still contributes its designation

glp-lookup-other $lookup

A global language pack only applies to the code system it supplements: another code system with the same code gets no German display or designation

glp-expand-de $expand

$expand in German: the displays come from the unreferenced global language pack, which is reported as a used-supplement

glp-expand-en $expand

$expand in English: the German global language pack has nothing to contribute, and the displays are the code system's own (reporting the pack as used is optional)

glp-expand-nl-unreferenced $expand

$expand in Dutch: a language pack that is not global is not used unless it is referenced, so the displays are the code system's own, and it is not a used-supplement

glp-own-expand-de $expand

Who wins in German when the code system has its own German designation for a code: the code system's own designation is the display for that code, the global language pack provides the display for the other code, and the pack is still reported as a used-supplement

glp-own-lookup-de $lookup

$lookup in German of a code with its own German designation: the display is the code system's own, and the global language pack's German designation is still listed, with its source

glp-own-validate-pack-display-de $validate-code

The global language pack's German display stays a valid display for a code whose own German designation is preferred: the result is true, and the display returned is the code system's own

glp-expand-pinned-other-version $expand

A supplement only applies to the version of the code system it names: a global language pack for glp-base|0.9.0 is not used on glp-base 1.0.0 (the only version the server has, chosen because the request names none), so the French displays are the code system's own, and it is not a used-supplement (reporting the German pack as used is optional, as in glp-expand-en)

glp-expand-pinned-other-version-required $expand

The same supplement, required with useSupplement: it does not apply to the version of the code system used, so the expansion fails

extension-codes general

Extension-codes supplements: a code system reserves a code space (codesystem-reservedCodeSpace) for users to define their own codes, and a CodeSystem supplement of type extension-codes defines codes in it, with displays. A global one (codesystem-supplement-global) is used whether or not it is referenced, as if the code system defined the codes; one that is not global is only used when it is referenced. A code in the reserved code space that nothing in scope defines is valid, with the code space's default display (default-display, or User-assigned). In a value set, a reserved code is a member of an include of all of the code system (so its expansion is unclosed) and of an include that lists it; a filter never selects one

ec-lookup-global $lookup

$lookup of a code defined by a global extension-codes supplement: it has the supplement's display, and the supplement is a used-supplement

ec-lookup-local-referenced $lookup

$lookup of a code defined by an extension-codes supplement that is not global, when the supplement is referenced (useSupplement): it has the supplement's display

ec-lookup-local-unreferenced $lookup

The same code when the supplement is not referenced: the code is in the reserved code space, so it is a valid code, with the code space's default display (User-assigned)

ec-lookup-undefined $lookup

$lookup of a code in the reserved code space that no supplement defines: it is a valid code, with the default display (User-assigned)

ec-lookup-default-display $lookup

$lookup of a code in a reserved code space whose codesystem-reservedCodeSpace extension has a default-display: the code has that display

ec-validate-global $cs-validate-code

$validate-code of a code defined by a global extension-codes supplement, with no display: the display is the supplement's

ec-validate-global-display $cs-validate-code

The same code with the supplement's display: valid

ec-validate-global-wrong-display $cs-validate-code

The same code with a different display: a global extension-codes supplement is as if the code system defined the code, so a wrong display is an error

ec-validate-global-wrong-display-lenient $cs-validate-code

The same, with lenient-display-validation: a wrong display is a warning

ec-validate-local-referenced $cs-validate-code

$validate-code of a code defined by an extension-codes supplement that is not global, when it is referenced, with no display: the display is the supplement's

ec-validate-local-referenced-display $cs-validate-code

The same code with the supplement's display: valid

ec-validate-local-referenced-wrong-display $cs-validate-code

The same code with a different display: the supplement's display is not the only correct one, so the code is valid, with a warning

ec-validate-local-unreferenced $cs-validate-code

The same code when the supplement is not referenced: a code in the reserved code space with only the default display (User-assigned), which is a placeholder, so another display is valid (with an information issue at most)

ec-validate-undefined $cs-validate-code

A code in the reserved code space that no supplement defines: valid, with the default display (User-assigned)

ec-validate-default-display $cs-validate-code

$validate-code of a code in a reserved code space with a default-display, with no display: the display is the default-display

ec-validate-outside $cs-validate-code

A code that is neither defined by the code system nor in its reserved code space: not valid

ec-validate-supplement-display $cs-validate-code

An extension-codes supplement can also give a display for a code the code system defines (outside the reserved code space): it acts as a language pack does, so its display is valid, and the code system's own display is still the one returned

ec-expand-enumerated $expand

$expand of a value set that lists codes from the reserved code space without displays: the global supplement's code gets its display, the others (a code from a supplement that is not referenced, and one that nothing defines) get the default display (User-assigned)

ec-expand-enumerated-referenced $expand

The same, with the supplement that is not global referenced (useSupplement): its code gets its display too

ec-expand-all $expand

$expand of all of the code system: the codes defined by extension-codes supplements are not included, only the code system's own - and since the code system has reserved code spaces, whose codes $validate-code accepts but the expansion can't list, the expansion is marked unclosed (valueset-unclosed)

ec-validate-global-referenced-wrong-display $cs-validate-code

A global supplement that is also referenced (useSupplement) is used once: a wrong display for a code the global supplement gives a second display lists each valid display once

ec-validate-global-referenced-wrong-display-lenient $cs-validate-code

The same, with lenient-display-validation: a warning

ec-lookup-global-referenced $lookup

$lookup of the same code, with the global supplement also referenced: the supplement's designation is there once, and it is a used-supplement once

ec-vs-validate-all-undefined $validate-code

$validate-code of a reserved code (X99, which nothing defines) against all of the code system (ec-all): the reserved codes are members, which is why ec-expand-all is unclosed: valid

ec-vs-validate-listed-undefined $validate-code

$validate-code of the reserved code X99 against A1 and the reserved code X99, listed: valid

ec-vs-validate-listed-a2 $validate-code

$validate-code of A2 (a code of the code system that isn't listed) against A1 and the reserved code X99, listed: not in the value set

ec-vs-expand-concept-in $expand

$expand of concept in A1,X99: A1

ec-vs-validate-concept-in-undefined $validate-code

$validate-code of the reserved code X99 against concept in A1,X99: not in the value set

ec-vs-expand-concept-not-in $expand

$expand of concept not-in A1: A2

ec-vs-validate-concept-not-in-undefined $validate-code

$validate-code of the reserved code X99 against concept not-in A1: not in the value set

ec-vs-expand-code-not-in $expand

$expand of code not-in A1: A2

ec-vs-validate-code-not-in-undefined $validate-code

$validate-code of the reserved code X99 against code not-in A1: not in the value set

ec-vs-expand-is-not-a $expand

$expand of concept is-not-a A1: A2

ec-vs-validate-is-not-a-undefined $validate-code

$validate-code of the reserved code X99 against concept is-not-a A1: not in the value set

ec-vs-expand-regex $expand

$expand of code regex X.*: matches only codes in the X code space: no codes

ec-vs-validate-regex-undefined $validate-code

$validate-code of the reserved code X99 against code regex X.*: matches only codes in the X code space: not in the value set

extension-codes-3166 tx.fhir.org

Extension-codes supplements for ISO 3166, whose user-assigned codes are its reserved code space. In the tx.fhir.org mode, since no general suite tests ISO 3166

ec-3166-validate-global $cs-validate-code

ISO 3166: a user-assigned code given a display by a global extension-codes supplement: the display is the supplement's

ec-3166-validate-global-wrong-display $cs-validate-code

The same code with a different display: an error (not just the hint for a user-assigned code), since the global supplement is as if the code system defined the code

ec-3166-validate-local-referenced $cs-validate-code

A user-assigned code given a display by an extension-codes supplement that is not global, when it is referenced: the display is the supplement's

ec-3166-validate-local-referenced-wrong-display $cs-validate-code

The same code with a different display: valid, with a warning

ec-3166-expand $expand

$expand of user-assigned codes: the one with a global extension-codes supplement gets its display, the other (from a supplement that is not referenced) does not

ec-3166-expand-referenced $expand

The same, with the supplement that is not global referenced: both get displays

extensions general

Testing proper handling of extensions, which depends on the extension

extensions-echo-all $expand

to be provided

extensions-echo-enumerated $expand

to be provided

extensions-echo-bad-supplement $expand

to be provided

validate-code-bad-supplement $validate-code

to be provided

validate-coding-bad-supplement $validate-code

to be provided

validate-coding-bad-supplement-url $cs-validate-code

to be provided

validate-codeableconcept-bad-supplement $validate-code

to be provided

validate-coding-good-supplement $validate-code

to be provided

validate-coding-good2-supplement $validate-code

to be provided

validate-code-inactive-display-lenient $cs-validate-code

Check handling of a deprecated designation (lenient display validation)

validate-code-inactive-display-notlenient $cs-validate-code

Check handling of a deprecated designation (strict display validation)

validate-code-inactive $cs-validate-code

Check handling of a deprecated concept

lookup-supplements-hierarchy-child $lookup

$lookup of a child concept with two supplements referenced: each supplement's designation is there once

lookup-supplements-hierarchy-grandchild $lookup

The same for a grandchild concept

validate-supplements-grandchild-wrong-display $cs-validate-code

$validate-code of the grandchild with a wrong display, displayLanguage de and two supplements referenced: the valid German display is listed once

validate-supplement-nolang-display $cs-validate-code

A supplement with no language (CodeSystem.language): its display is a correct display in any language - here with displayLanguage de

validate-supplement-nolang-designation $cs-validate-code

The same for a designation with no language in a supplement with no language

validate-supplement-nolang-other-lang $cs-validate-code

A designation that does have a language (fr), in the same supplement, is only a display in that language: with displayLanguage de it is a wrong display

expand-supplement-prop $expand

A filter on a property that the supplement defines (prop1), not the code system: while the supplement is in use, the filter selects the codes the supplement gives that value (code5)

expand-supplement-prop-base $expand

The same filter with a filter on the code system (concept in code4,code5): a code has to pass both, so code4 is not in the expansion

validate-supplement-prop-base-code5 $validate-code

$validate-code against the same value set: code5 passes both filters (and is deprecated, which is reported as it is for a value set that lists it)

validate-supplement-prop-base-code4 $validate-code

$validate-code against the same value set: code4 passes the code system filter, but the supplement doesn't give it prop1 = value1, so it is not in the value set

expand-supplement-version $expand

Two versions of the same supplement are in scope - the server has 1.0.0, which the value set names without a version, and the request passes 0.9.0-request in tx-resource and asks for it by version with useSupplement url|version: only the version asked for is used (not the later one), and used-supplement reports that exact version (0.9.0-request, whose Dutch display is the one in the expansion). The supplement has its own url, used by no other test, so that the request's version can't affect another test

validation general

Testing various validation parameter combinations

validation-simple-code-good $validate-code

to be provided

validation-simple-child-of-child $validate-code

child-of picks up a direct child - here the hierarchy is stated by nesting

validation-simple-child-of-grandchild $validate-code

and it stops there: a grandchild is not a child

validation-simple-concept-not-in-listed $validate-code

a code listed in a concept not-in filter is not in the value set

validation-simple-concept-not-in-child-of-listed $validate-code

a child of a code listed in a concept not-in filter is in the value set: not-in excludes only the codes it lists

validation-simple-code-not-in-listed $validate-code

a code listed in a code not-in filter is not in the value set

validation-simple-code-not-in-other $validate-code

a code not listed in a code not-in filter is in the value set

validation-simple-code-implied-good $validate-code

to be provided

validation-simple-coding-good $validate-code

to be provided

validation-simple-codeableconcept-good $validate-code

to be provided

validation-simple-code-bad-code $validate-code

to be provided

validation-simple-code-implied-bad-code $validate-code

to be provided

validation-simple-coding-bad-code $validate-code

to be provided

validation-simple-coding-bad-code-inactive $validate-code

to be provided

validation-simple-codeableconcept-bad-code $validate-code

to be provided

validation-simple-code-bad-valueSet $validate-code

to be provided

validation-simple-coding-bad-valueSet $validate-code

to be provided

validation-simple-codeableconcept-bad-valueSet $validate-code

to be provided

validation-simple-code-bad-import $validate-code

to be provided

validation-simple-coding-bad-import $validate-code

to be provided

validation-simple-codeableconcept-bad-import $validate-code

to be provided

validation-simple-code-bad-system $validate-code

to be provided

validation-simple-coding-bad-system $validate-code

to be provided

validation-simple-codeableconcept-unknown-system $validate-code

A CodeableConcept with a coding from an unknown code system alongside a coding that is in the value set. The unknown system cannot be checked, but membership is satisfied by the other coding, so the result is true with a warning

validation-simple-coding-bad-system2 $validate-code

to be provided

validation-simple-coding-bad-system-local $validate-code

to be provided

validation-simple-coding-no-system $validate-code

to be provided

validation-simple-codeableconcept-bad-system $validate-code

to be provided

validation-simple-code-good-display $validate-code

to be provided

validation-simple-coding-good-display $validate-code

to be provided

validation-simple-codeableconcept-good-display $validate-code

to be provided

validation-simple-code-bad-display-lenient $validate-code

a bad display, with lenient display validation - a warning, and the code is valid

validation-simple-code-bad-display-notlenient $validate-code

a bad display, with strict display validation - an error, and the code is not valid

validation-simple-code-bad-display-ws $validate-code

to be provided

validation-simple-coding-bad-display $validate-code

to be provided

validation-simple-codeableconcept-bad-display $validate-code

to be provided

validation-simple-code-bad-display-warning $validate-code

to be provided

validation-simple-coding-bad-display-warning $validate-code

to be provided

validation-simple-codeableconcept-bad-display-warning $validate-code

to be provided

validation-simple-code-good-language $validate-code

to be provided

validation-simple-coding-good-language $validate-code

to be provided

validation-simple-codeableconcept-good-language $validate-code

to be provided

validation-simple-code-bad-language $validate-code

to be provided

validation-simple-code-good-regex $validate-code

to be provided

validation-simple-code-bad-regex $validate-code

to be provided

validation-simple-code-regex-none $validate-code

A code that exists in the code system is not in a value set whose only include is a valid regex filter that matches no codes

validation-simple-coding-bad-language $validate-code

to be provided

validation-simple-coding-bad-language-header $validate-code

to be provided

validation-simple-coding-bad-language-vs $validate-code

to be provided

validation-simple-coding-bad-language-vslang $validate-code

to be provided

validation-simple-codeableconcept-bad-language $validate-code

to be provided

validation-simple-code-good-language-none $validate-code

Validate a code where the display is a valid designation in the code system's default language (en), and the requested displayLanguage (de) has no displays for the code. The display is valid, with an informational message

validation-simple-code-bad-language-none $validate-code

Validate a code where the display matches no display or designation at all, and the requested displayLanguage (de) has no displays for the code. The display is invalid

validation-simple-coding-good-language-none $validate-code

Validate a Coding where the display is a valid designation in the code system's default language (en), and the requested displayLanguage (de) has no displays for the code. The display is valid, with an informational message

validation-simple-coding-bad-language-none $validate-code

Validate a Coding where the display matches no display or designation at all, and the requested displayLanguage (de) has no displays for the code. The display is invalid

validation-simple-codeableconcept-good-language-none $validate-code

Validate a CodeableConcept where the coding display is a valid designation in the code system's default language (en), and the requested displayLanguage (de) has no displays for the code. The display is valid, with an informational message

validation-simple-codeableconcept-bad-language-none $validate-code

Validate a CodeableConcept where the coding display matches no display or designation at all, and the requested displayLanguage (de) has no displays for the code. The display is invalid

validation-complex-codeableconcept-full $validate-code

to be provided

validation-complex-codeableconcept-vsonly $validate-code

to be provided

validation-cs-code-good $cs-validate-code

to be provided

validation-cs-code-bad-code $cs-validate-code

to be provided

validation-contained-good $validate-code

Validation where the compose refers to a contained value set (valid code)

validation-contained-bad $validate-code

Validation where the compose refers to a contained value set (invalid code)

validation-contained-nested $validate-code

Validation where the compose refers to a contained value set, which itself refers to another contained value set

validation-missing-vs-code-no-system $validate-code

A code parameter with no system and no inferSystem: the server cannot tell what code system the code is from, so the request is an error

validation-missing-vs-system-no-code $validate-code

A system parameter but no code at all: there is nothing to validate, so the request is an error

validation-missing-vs-nothing $validate-code

No code, coding or codeableConcept at all: there is nothing to validate, so the request is an error

validation-missing-vs-coding-no-code $validate-code

A Coding with a system but no code. The parameter was provided, so this is a validation outcome (result = false), not a request error. Only one issue: the Coding cannot be validated. There is no code to report as not being in the value set

validation-missing-vs-coding-display-only $validate-code

A Coding with neither system nor code - only a display. That is one problem, not two: the server reports a single warning saying that neither a system nor a code was provided, rather than one message about each

validation-missing-vs-cc-no-system $validate-code

A CodeableConcept whose only coding has no system: the coding cannot be validated (warning - inferSystem was not asked for), it is not a valid coding for the value set (information), and the CodeableConcept as a whole fails (error)

validation-missing-vs-cc-no-code $validate-code

A CodeableConcept whose only coding has a system but no code: the coding cannot be validated, and the CodeableConcept as a whole fails

validation-missing-vs-cc-text-only $validate-code

A CodeableConcept with text and no codings at all: nothing to validate against the value set, so the CodeableConcept fails with a single error

validation-missing-vs-cc-mixed $validate-code

A CodeableConcept with a systemless coding alongside a valid one: the valid coding carries the result (true), and the systemless coding is reported as a warning against that coding

validation-missing-cs-code-no-url $cs-validate-code

A code parameter with no url: there is no code system to validate the code against, so the request is an error

validation-missing-cs-url-no-code $cs-validate-code

A url but no code, coding or codeableConcept: there is nothing to validate, so the request is an error

validation-missing-cs-nothing $cs-validate-code

No parameters at all: the request is an error

validation-missing-cs-coding-no-code $cs-validate-code

A Coding with a system but no code, validated against the code system: the parameter was provided, so this is a validation outcome (result = false), not a request error

validation-missing-cs-coding-no-system $cs-validate-code

A Coding with a code but no system, and no url either: nothing identifies the code system, so the code cannot be validated. The issue is a warning - only the caller knows whether a code with no system is acceptable in its context - but the code did not validate, so result is false

validation-missing-cs-cc-no-system $cs-validate-code

A CodeableConcept whose only coding has no system, validated against the code system. The issue is a warning, and is reported against the coding, not the CodeableConcept

validation-missing-cs-cc-no-code $cs-validate-code

A CodeableConcept whose only coding has a system but no code, validated against the code system

validation-missing-vs-coding-no-system-infer $validate-code

A Coding with no system and inferSystem = true: inferSystem is defined only for the code parameter, so it does not apply to a Coding - the server ignores it, and reports the systemless coding exactly as it does without it

validation-missing-vs-cc-no-system-infer $validate-code

A CodeableConcept whose only coding has no system, with inferSystem = true: inferSystem is defined only for the code parameter, so it does not apply to the codings of a CodeableConcept, and the response is the same as without it

validation-vn-cs-code $cs-validate-code

CodeSystem $validate-code, code with no version. The code system has versionNeeded = true, so a warning is expected

validation-vn-cs-coding $cs-validate-code

CodeSystem $validate-code, Coding with no version. The code system has versionNeeded = true, so a warning is expected

validation-vn-cs-cc $cs-validate-code

CodeSystem $validate-code, CodeableConcept whose coding has no version. The code system has versionNeeded = true, so a warning is expected, against the coding

validation-vn-cs-coding-version-param $cs-validate-code

CodeSystem $validate-code, Coding with no version, version parameter 1.0.0. The version parameter is specific to this call, and doesn't travel with the coding, so the warning is still expected

validation-vn-cs-coding-versioned $cs-validate-code

CodeSystem $validate-code, Coding with version 1.0.0. The code system has versionNeeded = true, and the version is present, so no warning

validation-vn-vs-code $validate-code

ValueSet $validate-code, code + system with no version. The code system has versionNeeded = true, so a warning is expected

validation-vn-vs-coding $validate-code

ValueSet $validate-code, Coding with no version. The code system has versionNeeded = true, so a warning is expected

validation-vn-vs-cc $validate-code

ValueSet $validate-code, CodeableConcept whose coding has no version. The code system has versionNeeded = true, so a warning is expected, against the coding

validation-vn-vs-coding-versioned $validate-code

ValueSet $validate-code, Coding with version 1.0.0. The code system has versionNeeded = true, and the version is present, so no warning

validation-vn-vs-coding-pinned $validate-code

ValueSet $validate-code, Coding with no version, value set pins the code system version to 1.0.0. The value set's version is specific to the value set, and doesn't travel with the coding, so the warning is still expected

validation-vn-vs-coding-force $validate-code

ValueSet $validate-code, Coding with no version, force-system-version 1.0.0. The parameter is specific to this call, and doesn't travel with the coding, so the warning is still expected

validation-vn-vs-coding-default $validate-code

ValueSet $validate-code, Coding with no version, system-version 1.0.0. The parameter is specific to this call, and doesn't travel with the coding, so the warning is still expected

version general

Testing various version issues. There's two versions of a code system, and three value sets that select different versions

version-simple-code-bad-version1 $validate-code

Code. Invalid CodeSystem version. No ValueSet version pinning. No version parameters

version-simple-coding-bad-version1 $validate-code

Coding. Invalid CodeSystem version. No ValueSet version pinning. No version parameters

version-simple-codeableconcept-bad-version1 $validate-code

CodeableConcept. Invalid CodeSystem version. No ValueSet version pinning. No version parameters

version-simple-codeableconcept-bad-version2 $validate-code

Check that a bad system with a version doesn't generate a warning that the version can't be found

version-simple-code-good-version $validate-code

Code. Valid CodeSystem version. ValueSet pinned to same version. No version parameters

version-simple-coding-good-version $validate-code

Coding. Valid CodeSystem version. ValueSet pinned to same version. No version parameters

version-simple-codeableconcept-good-version $validate-code

CodeableConcept. Valid CodeSystem version. ValueSet pinned to same version. No version parameters

version-version-profile-none $validate-code

to be provided

version-version-profile-default $validate-code

to be provided

validation-version-profile-coding $validate-code

to be provided

coding-vnn-vsnn $validate-code

Coding. No CodeSystem version. No ValueSet version pinning. No version parameters

coding-v10-vs1w $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.x. No version parameters

coding-v10-vs1wb $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.x. No version parameters

coding-v10-vs10 $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.0. No version parameters

coding-v10-vs20 $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.2. No version parameters

coding-v10-vsbb $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 2.4 (bad). No version parameters

coding-v10-vsbb $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 2.4 (bad). No version parameters

coding-v10-vsnn $validate-code

Coding. CodeSystem version 1.0. No ValueSet version pinning. No version parameters

coding-vbb-vs10 $validate-code

Coding. CodeSystem version 2.4 (bad). ValueSet version pinned to 1.0. No version parameters

coding-vbb-vsnn $validate-code

Coding. CodeSystem version 2.4 (bad). No ValueSet version pinning. No version parameters

coding-vnn-vs1w $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.x. No version parameters

coding-vnn-vs1wb $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.x. No version parameters

coding-vnn-vs10 $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.0. No version parameters

coding-vnn-vsbb $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 2.4 (bad). No version parameters

coding-vnn-vsnn-default $validate-code

Coding. No CodeSystem version. No ValueSet version pinning. Version Parameter: default to 1.2.0

coding-v10-vs1w-default $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.x. Version Parameter: default to 1.2.0

coding-v10-vs1wb-default $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.x. Version Parameter: default to 1.2.0

coding-v10-vs10-default $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.0. Version Parameter: default to 1.2.0

coding-v10-vs20-default $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.2. Version Parameter: default to 1.2.0

coding-v10-vsbb-default $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 2.4 (bad). Version Parameter: default to 1.2.0

coding-v10-vsnn-default $validate-code

Coding. CodeSystem version 1.0. No ValueSet version pinning. Version Parameter: default to 1.2.0

coding-vbb-vs10-default $validate-code

Coding. CodeSystem version 2.4 (bad). ValueSet version pinned to 1.0. Version Parameter: default to 1.2.0

coding-vbb-vsnn-default $validate-code

Coding. CodeSystem version 2.4 (bad). No ValueSet version pinning. Version Parameter: default to 1.2.0

coding-vnn-vs1w-default $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.x. Version Parameter: default to 1.2.0

coding-vnn-vs1wb-default $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.x. Version Parameter: default to 1.2.0

coding-vnn-vs10-default $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.0. Version Parameter: default to 1.2.0

coding-vnn-vsbb-default $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 2.4 (bad). Version Parameter: default to 1.2.0

coding-vnn-vsnn-check $validate-code

Coding. No CodeSystem version. No ValueSet version pinning. Version Parameter: check is 1.2.0

coding-v10-vs1w-check $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.x. Version Parameter: check is 1.2.0

coding-v10-vs1wb-check $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.x. Version Parameter: check is 1.2.0

coding-v10-vs10-check $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.0. Version Parameter: check is1.2.0

coding-v10-vs20-check $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.2. Version Parameter: check is 1.2.0

coding-v10-vsbb-check $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 2.4 (bad). Version Parameter: check is 1.2.0

coding-v10-vsnn-check $validate-code

Coding. CodeSystem version 1.0. No ValueSet version pinning. Version Parameter: check is 1.2.0

coding-vbb-vs10-check $validate-code

Coding. CodeSystem version 2.4 (bad). ValueSet version pinned to 1.0. Version Parameter: check is 1.2.0

coding-vbb-vsnn-check $validate-code

Coding. CodeSystem version 2.4 (bad). No ValueSet version pinning. Version Parameter: check is 1.2.0

coding-vnn-vs1w-check $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.x. Version Parameter: check is 1.2.0

coding-vnn-vs1wb-check $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.x. Version Parameter: check is 1.2.0

coding-vnn-vs10-check $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.0. Version Parameter: check is 1.2.0

coding-vnn-vsbb-check $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 2.4 (bad). Version Parameter: check is 1.2.0

coding-vnn-vsnn-force $validate-code

Coding. No CodeSystem version. No ValueSet version pinning. Version Parameter: force to 1.2.0

coding-v10-vs1w-force $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.x. Version Parameter: force to 1.2.0

coding-v10-vs1wb-force $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.x. Version Parameter: force to 1.2.0

coding-v10-vs10-force $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.0. Version Parameter: force to 1.2.0

coding-v10-vs20-force $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.2. Version Parameter: force to 1.2.0

coding-v10-vsbb-force $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 2.4 (bad). Version Parameter: force to 1.2.0

coding-v10-vsnn-force $validate-code

Coding. CodeSystem version 1.0. No ValueSet version pinning. Version Parameter: force to 1.2.0

coding-vbb-vs10-force $validate-code

Coding. CodeSystem version 2.4 (bad). ValueSet version pinned to 1.0. Version Parameter: force to 1.2.0

coding-vbb-vsnn-force $validate-code

Coding. CodeSystem version 2.4 (bad). No ValueSet version pinning. Version Parameter: force to 1.2.0

coding-vnn-vs1w-force $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.x. Version Parameter: force to 1.2.0

coding-vnn-vs1wb-force $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.x. Version Parameter: force to 1.2.0

coding-vnn-vs10-force $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.0. Version Parameter: force to 1.2.0

coding-vnn-vsbb-force $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 2.4 (bad). Version Parameter: force to 1.2.0

codeableconcept-vnn-vsnn $validate-code

Coding. No CodeSystem version. No ValueSet version pinning. No version parameters

codeableconcept-v10-vs1w $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.x. No version parameters

codeableconcept-v10-vs1wb $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.x. No version parameters

codeableconcept-v10-vs10 $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.0. No version parameters

codeableconcept-v10-vs20 $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.2. No version parameters

codeableconcept-v10-vsbb $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 2.4 (bad). No version parameters

codeableconcept-v10-vsbb $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 2.4 (bad). No version parameters

codeableconcept-v10-vsnn $validate-code

Coding. CodeSystem version 1.0. No ValueSet version pinning. No version parameters

codeableconcept-vbb-vs10 $validate-code

Coding. CodeSystem version 2.4 (bad). ValueSet version pinned to 1.0. No version parameters

codeableconcept-vbb-vsnn $validate-code

Coding. CodeSystem version 2.4 (bad). No ValueSet version pinning. No version parameters

codeableconcept-vnn-vs1w $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.x. No version parameters

codeableconcept-vnn-vs1wb $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.x. No version parameters

codeableconcept-vnn-vs10 $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.0. No version parameters

codeableconcept-vnn-vsbb $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 2.4 (bad). No version parameters

codeableconcept-vnn-vsnn-default $validate-code

Coding. No CodeSystem version. No ValueSet version pinning. Version Parameter: default to 1.2.0

codeableconcept-v10-vs1w-default $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.x. Version Parameter: default to 1.2.0

codeableconcept-v10-vs1wb-default $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.x. Version Parameter: default to 1.2.0

codeableconcept-v10-vs10-default $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.0. Version Parameter: default to 1.2.0

codeableconcept-v10-vs20-default $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.2. Version Parameter: default to 1.2.0

codeableconcept-v10-vsbb-default $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 2.4 (bad). Version Parameter: default to 1.2.0

codeableconcept-v10-vsnn-default $validate-code

Coding. CodeSystem version 1.0. No ValueSet version pinning. Version Parameter: default to 1.2.0

codeableconcept-vbb-vs10-default $validate-code

Coding. CodeSystem version 2.4 (bad). ValueSet version pinned to 1.0. Version Parameter: default to 1.2.0

codeableconcept-vbb-vsnn-default $validate-code

Coding. CodeSystem version 2.4 (bad). No ValueSet version pinning. Version Parameter: default to 1.2.0

codeableconcept-vnn-vs1w-default $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.x. Version Parameter: default to 1.2.0

codeableconcept-vnn-vs1wb-default $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.x. Version Parameter: default to 1.2.0

codeableconcept-vnn-vs10-default $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.0. Version Parameter: default to 1.2.0

codeableconcept-vnn-vsbb-default $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 2.4 (bad). Version Parameter: default to 1.2.0

codeableconcept-vnn-vsnn-check $validate-code

Coding. No CodeSystem version. No ValueSet version pinning. Version Parameter: check is 1.2.0

codeableconcept-v10-vs1w-check $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.x. Version Parameter: check is 1.2.0

codeableconcept-v10-vs1wb-check $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.x. Version Parameter: check is 1.2.0

codeableconcept-v10-vs10-check $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.0. Version Parameter: check is1.2.0

codeableconcept-v10-vs20-check $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.2. Version Parameter: check is 1.2.0

codeableconcept-v10-vsbb-check $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 2.4 (bad). Version Parameter: check is 1.2.0

codeableconcept-v10-vsnn-check $validate-code

Coding. CodeSystem version 1.0. No ValueSet version pinning. Version Parameter: check is 1.2.0

codeableconcept-vbb-vs10-check $validate-code

Coding. CodeSystem version 2.4 (bad). ValueSet version pinned to 1.0. Version Parameter: check is 1.2.0

codeableconcept-vbb-vsnn-check $validate-code

Coding. CodeSystem version 2.4 (bad). No ValueSet version pinning. Version Parameter: check is 1.2.0

codeableconcept-vnn-vs1w-check $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.x. Version Parameter: check is 1.2.0

codeableconcept-vnn-vs1wb-check $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.x. Version Parameter: check is 1.2.0

codeableconcept-vnn-vs10-check $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.0. Version Parameter: check is 1.2.0

codeableconcept-vnn-vsbb-check $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 2.4 (bad). Version Parameter: check is 1.2.0

codeableconcept-vnn-vsnn-force $validate-code

Coding. No CodeSystem version. No ValueSet version pinning. Version Parameter: force to 1.2.0

codeableconcept-v10-vs1w-force $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.x. Version Parameter: force to 1.2.0

codeableconcept-v10-vs1wb-force $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.x. Version Parameter: force to 1.2.0

codeableconcept-v10-vs10-force $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.0. Version Parameter: force to 1.2.0

codeableconcept-v10-vs20-force $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 1.2. Version Parameter: force to 1.2.0

codeableconcept-v10-vsbb-force $validate-code

Coding. CodeSystem version 1.0. ValueSet version pinned to 2.4 (bad). Version Parameter: force to 1.2.0

codeableconcept-v10-vsnn-force $validate-code

Coding. CodeSystem version 1.0. No ValueSet version pinning. Version Parameter: force to 1.2.0

codeableconcept-vbb-vs10-force $validate-code

Coding. CodeSystem version 2.4 (bad). ValueSet version pinned to 1.0. Version Parameter: force to 1.2.0

codeableconcept-vbb-vsnn-force $validate-code

Coding. CodeSystem version 2.4 (bad). No ValueSet version pinning. Version Parameter: force to 1.2.0

codeableconcept-vnn-vs1w-force $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.x. Version Parameter: force to 1.2.0

codeableconcept-vnn-vs1wb-force $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.x. Version Parameter: force to 1.2.0

codeableconcept-vnn-vs10-force $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 1.0. Version Parameter: force to 1.2.0

codeableconcept-vnn-vsbb-force $validate-code

Coding. No CodeSystem version. ValueSet version pinned to 2.4 (bad). Version Parameter: force to 1.2.0

code-vnn-vsnn $validate-code

code. No CodeSystem version. No ValueSet version pinning. No version parameters

code-v10-vs1w $validate-code

code. CodeSystem version 1.0. ValueSet version pinned to 1.x. No version parameters

code-v10-vs1wb $validate-code

code. CodeSystem version 1.0. ValueSet version pinned to 1.x. No version parameters

code-v10-vs10 $validate-code

code. CodeSystem version 1.0. ValueSet version pinned to 1.0. No version parameters

code-v10-vs20 $validate-code

code. CodeSystem version 1.0. ValueSet version pinned to 1.2. No version parameters

code-v10-vsbb $validate-code

code. CodeSystem version 1.0. ValueSet version pinned to 2.4 (bad). No version parameters

code-v10-vsnn $validate-code

code. CodeSystem version 1.0. No ValueSet version pinning. No version parameters

code-vbb-vs10 $validate-code

code. CodeSystem version 2.4 (bad). ValueSet version pinned to 1.0. No version parameters

code-vbb-vsnn $validate-code

code. CodeSystem version 2.4 (bad). No ValueSet version pinning. No version parameters

code-vnn-vs1w $validate-code

code. No CodeSystem version. ValueSet version pinned to 1.x. No version parameters

code-vnn-vs1wb $validate-code

code. No CodeSystem version. ValueSet version pinned to 1.x. No version parameters

code-vnn-vs10 $validate-code

code. No CodeSystem version. ValueSet version pinned to 1.0. No version parameters

code-vnn-vsbb $validate-code

code. No CodeSystem version. ValueSet version pinned to 2.4 (bad). No version parameters

code-vnn-vsnn-default $validate-code

code. No CodeSystem version. No ValueSet version pinning. Version Parameter: default to 1.2.0

code-v10-vs1w-default $validate-code

code. CodeSystem version 1.0. ValueSet version pinned to 1.x. Version Parameter: default to 1.2.0

code-v10-vs1wb-default $validate-code

code. CodeSystem version 1.0. ValueSet version pinned to 1.x. Version Parameter: default to 1.2.0

code-v10-vs10-default $validate-code

code. CodeSystem version 1.0. ValueSet version pinned to 1.0. Version Parameter: default to 1.2.0

code-v10-vs20-default $validate-code

code. CodeSystem version 1.0. ValueSet version pinned to 1.2. Version Parameter: default to 1.2.0

code-v10-vsbb-default $validate-code

code. CodeSystem version 1.0. ValueSet version pinned to 2.4 (bad). Version Parameter: default to 1.2.0

code-v10-vsnn-default $validate-code

code. CodeSystem version 1.0. No ValueSet version pinning. Version Parameter: default to 1.2.0

code-vbb-vs10-default $validate-code

code. CodeSystem version 2.4 (bad). ValueSet version pinned to 1.0. Version Parameter: default to 1.2.0

code-vbb-vsnn-default $validate-code

code. CodeSystem version 2.4 (bad). No ValueSet version pinning. Version Parameter: default to 1.2.0

code-vnn-vs1wb-default $validate-code

code. No CodeSystem version. ValueSet version pinned to 1.x. Version Parameter: default to 1.2.0

code-vnn-vs10-default $validate-code

code. No CodeSystem version. ValueSet version pinned to 1.0. Version Parameter: default to 1.2.0

code-vnn-vsbb-default $validate-code

code. No CodeSystem version. ValueSet version pinned to 2.4 (bad). Version Parameter: default to 1.2.0

code-vnn-vsnn-check $validate-code

code. No CodeSystem version. No ValueSet version pinning. Version Parameter: check is 1.2.0

code-v10-vs1w-check $validate-code

code. CodeSystem version 1.0. ValueSet version pinned to 1.x. Version Parameter: check is 1.2.0

code-v10-vs1wb-check $validate-code

code. CodeSystem version 1.0. ValueSet version pinned to 1.x. Version Parameter: check is 1.2.0

code-v10-vs10-check $validate-code

code. CodeSystem version 1.0. ValueSet version pinned to 1.0. Version Parameter: check is1.2.0

code-v10-vs20-check $validate-code

code. CodeSystem version 1.0. ValueSet version pinned to 1.2. Version Parameter: check is 1.2.0

code-v10-vsbb-check $validate-code

code. CodeSystem version 1.0. ValueSet version pinned to 2.4 (bad). Version Parameter: check is 1.2.0

code-v10-vsnn-check $validate-code

code. CodeSystem version 1.0. No ValueSet version pinning. Version Parameter: check is 1.2.0

code-vbb-vs10-check $validate-code

code. CodeSystem version 2.4 (bad). ValueSet version pinned to 1.0. Version Parameter: check is 1.2.0

code-vbb-vsnn-check $validate-code

code. CodeSystem version 2.4 (bad). No ValueSet version pinning. Version Parameter: check is 1.2.0

code-vnn-vs1w-check $validate-code

code. No CodeSystem version. ValueSet version pinned to 1.x. Version Parameter: check is 1.2.0

code-vnn-vs1wb-check $validate-code

code. No CodeSystem version. ValueSet version pinned to 1.x. Version Parameter: check is 1.2.0

code-vnn-vs10-check $validate-code

code. No CodeSystem version. ValueSet version pinned to 1.0. Version Parameter: check is 1.2.0

code-vnn-vsbb-check $validate-code

code. No CodeSystem version. ValueSet version pinned to 2.4 (bad). Version Parameter: check is 1.2.0

code-vnn-vsnn-force $validate-code

code. No CodeSystem version. No ValueSet version pinning. Version Parameter: force to 1.2.0

code-v10-vs1w-force $validate-code

code. CodeSystem version 1.0. ValueSet version pinned to 1.x. Version Parameter: force to 1.2.0

code-v10-vs1wb-force $validate-code

code. CodeSystem version 1.0. ValueSet version pinned to 1.x. Version Parameter: force to 1.2.0

code-v10-vs10-force $validate-code

code. CodeSystem version 1.0. ValueSet version pinned to 1.0. Version Parameter: force to 1.2.0

code-v10-vs20-force $validate-code

code. CodeSystem version 1.0. ValueSet version pinned to 1.2. Version Parameter: force to 1.2.0

code-v10-vsbb-force $validate-code

code. CodeSystem version 1.0. ValueSet version pinned to 2.4 (bad). Version Parameter: force to 1.2.0

code-v10-vsnn-force $validate-code

code. CodeSystem version 1.0. No ValueSet version pinning. Version Parameter: force to 1.2.0

code-vbb-vs10-force $validate-code

code. CodeSystem version 2.4 (bad). ValueSet version pinned to 1.0. Version Parameter: force to 1.2.0

code-vbb-vsnn-force $validate-code

code. CodeSystem version 2.4 (bad). No ValueSet version pinning. Version Parameter: force to 1.2.0

code-vnn-vs1w-force $validate-code

code. No CodeSystem version. ValueSet version pinned to 1.x. Version Parameter: force to 1.2.0

code-vnn-vs1wb-force $validate-code

code. No CodeSystem version. ValueSet version pinned to 1.x. Version Parameter: force to 1.2.0

code-vnn-vs10-force $validate-code

code. No CodeSystem version. ValueSet version pinned to 1.0. Version Parameter: force to 1.2.0

code-vnn-vsbb-force $validate-code

code. No CodeSystem version. ValueSet version pinned to 2.4 (bad). Version Parameter: force to 1.2.0

code-vnn-vsmix-1 $validate-code

code (1). No CodeSystem version. ValueSet version includes both versions of the code system. No Version Parameter

code-vnn-vsmix-2 $validate-code

code (2). No CodeSystem version. ValueSet version includes both versions of the code system. No Version Parameter

vs-expand-all-v $expand

version specific expand tests

vs-expand-all-v1 $expand

version specific expand tests

vs-expand-all-v2 $expand

version specific expand tests

vs-expand-v-mixed $expand

version specific expand tests

vs-expand-v-n-request $expand

version specific expand tests

vs-expand-v-w $expand

version specific expand tests

vs-expand-v-wb $expand

version specific expand tests

vs-expand-v1 $expand

version specific expand tests

vs-expand-v2 $expand

version specific expand tests

vs-expand-all-v-force $expand

version specific expand tests

vs-expand-all-v1-force $expand

version specific expand tests

vs-expand-all-v2-force $expand

version specific expand tests

vs-expand-v-mixed-force $expand

version specific expand tests

vs-expand-v-n-force-request $expand

version specific expand tests

vs-expand-v-w-force $expand

version specific expand tests

vs-expand-v-wb-force $expand

version specific expand tests

vs-expand-v1-force $expand

version specific expand tests

vs-expand-v2-force $expand

version specific expand tests

vs-expand-stale-import $expand

A value set imports one that carries an expansion made from version 1.0.0 of the code system; the server has 1.2.0, which is what an expansion of its compose uses with no version asked for. The stale expansion is not used: the imported value set is expanded from its compose

vs-expand-stale-import-force $expand

As vs-expand-stale-import, with force-system-version naming 1.2.0: the imported value set's expansion from 1.0.0 doesn't match the forced version, so it's expanded from its compose

vs-expand-all-v-default $expand

version specific expand tests

vs-expand-all-v1-default $expand

version specific expand tests

vs-expand-all-v2-default $expand

version specific expand tests

vs-expand-v-mixed-default $expand

version specific expand tests

vs-expand-v-n-default-request $expand

version specific expand tests

vs-expand-v-w-default $expand

version specific expand tests

vs-expand-v-wb-default $expand

version specific expand tests

vs-expand-v1-default $expand

version specific expand tests

vs-expand-v2-default $expand

version specific expand tests

vs-expand-all-v-check $expand

version specific expand tests

vs-expand-all-v1-check $expand

version specific expand tests

vs-expand-all-v2-check $expand

version specific expand tests

vs-expand-v-mixed-check $expand

version specific expand tests

vs-expand-v-n-check-request $expand

version specific expand tests

vs-expand-v-w-check $expand

version specific expand tests

vs-expand-v-wb-check $expand

version specific expand tests

vs-expand-v1-check $expand

version specific expand tests

vs-expand-v2-check $expand

version specific expand tests

vs-expand-versionless $expand

check expand without any version

overload general

A set of tests that test out handling of value sets that cross versions of the same code system

expand-all $expand

Expanding two versions of the same code system

expand-all-versioned $expand

Expanding two versions of the same code system, versioned

expand-all-merged $expand

Expanding two versions of the same code system, merging versions

expand-enum-good $expand

Expanding two versions of the same code system, codes selected from each version

expand-enum-bad $expand

Expanding two versions of the same code system, codes selected from both versions - but you can't do this: code3 is not in version 2.0.0, which is the one used. The server may refuse to expand the value set (4xx), or expand it without the invalid code, saying the include referred to an invalid code in an expansion-issue (200)

expand-exclude $expand

Excluding one version of the code system from the other (cheap diff analysis)

expand-exclude-versioned $expand

Excluding one version of the code system from the other (cheap diff analysis), versioned

expand-exclude-merged $expand

Excluding one version of the code system from the other (cheap diff analysis), merging versions

validate-all-good $validate-code

Is code in value set - in both versions

validate-all-good2 $validate-code

Is code in value set - in both versions, but display from the second

validate-all-good3 $validate-code

Is code in value set - in one version

validate-all-good4 $validate-code

Is code in value set - in one versions

validate-all-bad2 $validate-code

Is code in value set - in one versions

validate-all-bad2v $validate-code

code from one version, display from the other

expand-all-sysver $expand

Tests whether a system-version parameter forcing v1 overrides the value set's explicit dual-version includes. It should not, since it's just a default

expand-exclude-enum $expand

Expands a value set that includes all of both versions but excludes only code2 from v1 by enumeration, testing version-scoped exclusion of individual codes.

expand-mixed $expand

Expands a value set with one versioned include (v1) and one unversioned include, testing how the server resolves the unversioned reference.

validate-bad-enum-code1 $validate-code

Validates that code1 is rejected by the enum-good value set, since it's not in the enumerated list.

validate-bad-exclude-code1 $validate-code

Validates that code1 is rejected by the exclude value set, since it exists in both versions and the v1 overlap is excluded.

validate-bad-unknown $validate-code

Validates that a completely nonexistent code (code99) fails against the value set.

validate-v1code2-wrongdisplay $validate-code

Validates that code1 with version pinned to 1.0.0 succeeds, confirming version-pinning works for a code present in both versions

validate-bad-v1code4 $validate-code

Validates that code4 with version explicitly pinned to 1.0.0 fails, since code4 only exists in v2.

validate-bad-v2code3 $validate-code

Validates that code3 with version explicitly pinned to 2.0.0 fails, since code3 only exists in v1.

validate-good-code2-v1display $validate-code

Tests the ambiguous case of code2 with display "Display 2" and no version pin, where the display matches v1 but not v2

validate-good-enum-code3 $validate-code

Validates code3 against the enum-good value set, which explicitly enumerates it from v1

validate-good-exclude-code4 $validate-code

Validates that code4 is accepted by the exclude value set, where it's the only code surviving the v1 exclusion.

validate-good-v1code1 $validate-code

Validates that code1 with version pinned to 1.0.0 succeeds, confirming version-pinning works for a code present in both versions.

validate-good-v1code2-display $validate-code

Validates that code2 with version=1.0.0 and display "Display 2" succeeds, since that's the correct display for v1.

validate-good2a $validate-code

Validates that a codeableConcept with both versions in it works fine.

fragment general

Testing handling a code system fragment

fragment-expansion $expand

check that the fragment is reported correctly

validation-fragment-code-good $validate-code

if a code is a in a fragment, then it's all ok

validation-fragment-coding-good $validate-code

if a code is a in a fragment, then it's all ok

validation-fragment-codeableconcept-good $validate-code

if a code is a in a fragment, then it's all ok

validation-fragment-code-bad-code $validate-code

if a code is not in the fragment, we can't call it invalid (code variant)

validation-fragment-coding-bad-code $validate-code

if a code is not in the fragment, we can't call it invalid (coding variant)

validation-fragment-codeableconcept-bad-code $validate-code

if a code is not in the fragment, we can't call it invalid (CodeableConcept variant)

big general

Testing handling a big code system

big-echo-no-limit $expand

to be provided

big-echo-zero-fifty-limit $expand

to be provided

big-echo-fifty-fifty-limit $expand

to be provided

big-circle-bang $expand

to be provided

big-circle-validate $validate-code

to be provided

other general

Misc tests based on issues submitted by users

dual-filter $expand

to be provided

validation-dual-filter-in $validate-code

to be provided

validation-dual-filter-out $validate-code

to be provided

errors general

Testing Various Error Conditions

unknown-system1 $validate-code

Value set & request refers to an unknown system

unknown-system2 $validate-code

Value set & request refers to an unknown system; request is a different unknown system

broken-filter-validate $validate-code

Make sure that filters without value cause an error

broken-filter2-validate $validate-code

Make sure that filters without value cause an error (extension only)

broken-filter-expand $expand

Make sure that filters without value cause an error

filter-modifier-expand $expand

A filter with a modifier extension the server doesn't know can't be used: the value set can't be expanded, and that's an error in the request (4xx), not the server

combination-ok $validate-code

A value set that contains two identical codes - validates ok

combination-bad $validate-code

A value set that contains two identical codes - error if inferSystem is true

infer-unknown-system $validate-code

inferSystem with a value set that includes all of a code system the server does not know: the code might be in it, so the system cannot be inferred - an error naming the unknown system

infer-unknown-system-import $validate-code

inferSystem with a value set that imports a value set, and includes all of a code system the server does not know: an error naming the unknown system

deprecated general

Testing Deprecated+Withdrawn warnings

withdrawn $expand

to be provided

not-withdrawn $expand

to be provided

withdrawn-validate $validate-code

to be provided

not-withdrawn-validate $validate-code

to be provided

experimental $expand

to be provided

experimental-validate $validate-code

to be provided

draft $expand

to be provided

draft-validate $validate-code

to be provided

vs-deprecation $expand

Deprecating a code in a valueset

deprecating-validate $validate-code

Validating a code that has been deprecated in the value set using a deprecated extension

deprecating-validate-2 $validate-code

Validating a code that has been deprecated in the value set

notSelectable general

Testing notSelectable

notSelectable-prop-all $expand

to be provided

notSelectable-noprop-all $expand

to be provided

notSelectable-reprop-all $expand

to be provided

notSelectable-unprop-all $expand

to be provided

notSelectable-prop-true $expand

to be provided

notSelectable-prop-trueUC $expand

to be provided

notSelectable-noprop-true $expand

to be provided

notSelectable-reprop-true $expand

to be provided

notSelectable-unprop-true $expand

to be provided

notSelectable-prop-false $expand

to be provided

notSelectable-noprop-false $expand

to be provided

notSelectable-reprop-false $expand

to be provided

notSelectable-unprop-false $expand

to be provided

notSelectable-prop-in $expand

to be provided

notSelectable-prop-out $expand

to be provided

notSelectable-prop-true-true $validate-code

to be provided

notSelectable-prop-trueUC-true $validate-code

to be provided

notSelectable-prop-in-true $validate-code

to be provided

notSelectable-prop-out-true $validate-code

to be provided

notSelectable-noprop-true-true $validate-code

to be provided

notSelectable-reprop-true-true $validate-code

to be provided

notSelectable-unprop-true-true $validate-code

to be provided

notSelectable-prop-true-false $validate-code

to be provided

notSelectable-prop-in-false $validate-code

to be provided

notSelectable-prop-in-unknown $validate-code

to be provided

notSelectable-prop-out-unknown $validate-code

to be provided

notSelectable-prop-out-false $validate-code

to be provided

notSelectable-noprop-true-false $validate-code

to be provided

notSelectable-reprop-true-false $validate-code

to be provided

notSelectable-unprop-true-false $validate-code

to be provided

notSelectable-prop-false-true $validate-code

to be provided

notSelectable-noprop-false-true $validate-code

to be provided

notSelectable-reprop-false-true $validate-code

to be provided

notSelectable-unprop-false-true $validate-code

to be provided

notSelectable-prop-false-false $validate-code

to be provided

notSelectable-noprop-false-false $validate-code

to be provided

notSelectable-reprop-false-false $validate-code

to be provided

notSelectable-unprop-false-false $validate-code

to be provided

notSelectable-noprop-true-unknown $validate-code

to be provided

notSelectable-reprop-true-unknown $validate-code

to be provided

notSelectable-unprop-true-unknown $validate-code

to be provided

notSelectable-prop-true-unknown $validate-code

to be provided

notSelectable-prop-false-unknown $validate-code

to be provided

notSelectable-noprop-false-unknown $validate-code

to be provided

notSelectable-reprop-false-unknown $validate-code

to be provided

notSelectable-unprop-false-unknown $validate-code

to be provided

notSelectable-prop-true-true-param-true $validate-code

to be provided

notSelectable-prop-true-true-param-false $validate-code

to be provided

notSelectable-prop-false-false-param-true $validate-code

to be provided

notSelectable-prop-false-false-param-false $validate-code

to be provided

inactive general

Testing Inactive codes

inactive-expand $expand

to be provided

inactive-inactive-expand $expand

to be provided

inactive-active-expand $expand

to be provided

inactive-1-validate $validate-code

to be provided

inactive-2-validate $validate-code

to be provided

inactive-3-validate $validate-code

to be provided

inactive-1a-validate $validate-code

to be provided

inactive-2a-validate $validate-code

to be provided

inactive-3a-validate $validate-code

to be provided

inactive-1b-validate $validate-code

to be provided

inactive-2b-validate $validate-code

to be provided

inactive-3b-validate $validate-code

to be provided

inactive-4-validate $validate-code

CodeableConcept with an active then an inactive coding: the inactive warning must name the inactive coding, not the first one

inactive-5-validate $validate-code

CodeableConcept with an inactive then an active coding: the later active coding must not suppress the inactive warning

inactive-enum-validate $validate-code

An inactive code that a value set lists (compose.inactive = true): it is in the value set, with a warning that it is inactive

inactive-enum-activeonly-validate $validate-code

The same with activeOnly = true: the code is validated against the value set as expanded with activeOnly, which has no inactive codes, so it is not in the value set - however the value set includes it (as for a value set that includes all the code system: validation-simple-coding-bad-code-inactive)

inactive-filter-activeonly-validate $validate-code

The same for a value set that selects the code with a filter: with activeOnly = true, the inactive code is not in the value set

case general

Test Case Sensitivity handling

case-insensitive-code1-1 $validate-code

to be provided

case-insensitive-code1-2 $validate-code

to be provided

case-insensitive-code1-3 $validate-code

to be provided

case-sensitive-code1-1 $validate-code

to be provided

case-sensitive-code1-2 $validate-code

to be provided

case-sensitive-code1-3 $validate-code

to be provided

translate general

Tests for ConceptMap.$translate

translate-1 $translate

A very simple translation, using sourceCode + sourceSystem

translate-1-coding $translate

The same translation, but naming the source concept with sourceCoding

translate-1-codeableconcept $translate

The same translation, but naming the source concept with sourceCodeableConcept

translate-1-r4-code $translate version: 4.0

The same translation, using the R4 input names: code + system, and targetsystem

translate-1-r4-coding $translate version: 4.0

The same translation, using the R4 input names: coding, and targetsystem

translate-1-r4-codeableconcept $translate version: 4.0

The same translation, using the R4 input names: codeableConcept, and targetsystem

translate-2 $translate

Testing different relationship types

translate-2b $translate

Testing different relationship types

translate-3 $translate

Testing different relationship types

translate-4 $translate

Testing nomap functionality. In R4 the ConceptMap states this with a codeless 'unmatched' target; either way the response reports noMap and no concept

translate-scope-1 $translate version: !4.0

targetScope with no targetSystem: the maps into the code systems the value set draws on apply, even when they don't name it as their targetScope. ValueSet/target-some (code1 and code4 of CodeSystem/target) is no map's targetScope; ConceptMap/full maps CodeSystem/source to CodeSystem/target, and code-1 maps to code1, which is in it

translate-scope-2 $translate version: !4.0

targetScope limits the operation to target codes that are members of the value set: code-2 maps to code2, which is not in ValueSet/target-some, so there is no translation (a message saying why is optional)

translate-scope-3 $translate version: !4.0

The same applies to a group's unmapped: code-5 has no element in ConceptMap/full, and its unmapped (fixed, code4) is in ValueSet/target-some

translate-scope-4 $translate version: !4.0

No map goes from CodeSystem/target to the code systems of ValueSet/target-some: the message names the source's code system and version (which version of the source it is decides which maps apply)

translate-scope-5 $translate version: !4.0

The same, with no version on the source: the message names the version the server took the source to be

translate2 general

Tests for ConceptMap.$translate

translate-5 $translate

Testing unmapped functionality

translate-5a $translate

Testing unmapped functionality which specifying a particular map

translate-5b $translate

Testing unmapped functionality which specifying a particular map

translate-6a $translate

A code that is not in any map's sourceScope has no applicable map: ConceptMap.sourceScope limits the scope of the map, so the map does not apply at all, and its unmapped does not fire either. code-6 is in CodeSystem/source but not in ValueSet/source, which is the sourceScope of full, othermap and othermap2; novs has no scope but no group for these code systems

translate-6b $translate

The same, but naming the map explicitly: nominating a map does not put an out of scope code into its scope, so there is still no outcome from it

translate-reverse-r5plus $translate version: !4.0

Same translation, but in reverse

translate-reverse-r5plus-a $translate version: !4.0

reverse is not allowed in R5

translate-reverse-r4 $translate version: 4.0

Same translation, but in reverse, using the reverse parameter

translate-reverse-r4-a $translate version: 4.0

Same translation, using the reverse parameter (e.g. double reversed)

translate-reverse-r4-b $translate version: 4.0

Same translation, but in reverse, not using the reverse parameter

tho general

Misc assorted test cases from tho

act-class $expand

act class - don't remember what bug this was testing for but now it tests for proper handling of retired and deprecated codes

act-class-activeonly $expand

tests for proper handling of retired and deprecated codes (part 2)

act-exclusion $expand

tests for proper handling of excluded codes

subsumes-act-class-property-parent $subsumes

a code subsumes a code that names it in a subsumedBy property; act-class is a flat list, so there is no nesting to read

subsumes-act-class-property-child $subsumes

the mirror of subsumes-act-class-property-parent

subsumes-act-class-transitive $subsumes

subsumption follows the whole chain of subsumedBy properties, five links here

subsumes-act-class-transitive-reverse $subsumes

the mirror of subsumes-act-class-transitive

subsumes-act-class-equivalent $subsumes

a code is equivalent to itself

subsumes-act-class-siblings $subsumes

two codes with the same subsumedBy do not subsume each other

subsumes-act-class-cross-branch $subsumes

both codes are under ACT, but neither is on the other's path to it

subsumes-act-class-multiple-parents-first $subsumes

ENTRY states subsumedBy twice: this is the first parent

subsumes-act-class-multiple-parents-second $subsumes

and this is the second - a relationship a nested hierarchy cannot express at all

subsumes-act-class-multiple-parents-crossed $subsumes

two parents of the same code are not thereby related to each other

subsumes-act-class-unknown-code $subsumes

codeB is not in the code system

validate-isa-self $validate-code

is-a includes the code named in the filter, not just what is under it

validate-isa-child $validate-code

a code that names the filter code in a subsumedBy property is in the value set

validate-isa-deep $validate-code

and so is one five property links below it

validate-isa-parent $validate-code

is-a runs downwards: the code above the filter code is not in the value set

validate-isa-other-branch $validate-code

a code in a different branch of the same code system is not in it either

validate-descendent-of-self $validate-code

descendent-of excludes the code named in the filter - the one thing that distinguishes it from is-a

validate-descendent-of-child $validate-code

everything below the filter code is in it, exactly as for is-a

validate-descendent-of-deep $validate-code

including the deep descendants

validate-isnota-self $validate-code

is-not-a excludes the code named in the filter as well as its descendants

validate-isnota-descendant $validate-code

a deep descendant of the filter code is excluded too, not just the direct children

validate-isnota-parent $validate-code

the code above the filter code is in an is-not-a value set

validate-isnota-other-branch $validate-code

and so is a code in a different branch

validate-child-of-child $validate-code

child-of picks up a direct child, which act-class states in a subsumedBy property rather than by nesting

validate-child-of-self $validate-code

child-of does not include the code named in the filter, unlike is-a

validate-child-of-grandchild $validate-code

and it stops at the direct children, which is what separates it from descendent-of

validate-isa-second-parent $validate-code

ENTRY is in an is-a on _ActContainer, the second of its two subsumedBy parents - a relationship nesting cannot express

validate-isa-second-parent-out $validate-code

a code under the other container is not in it

validate-isa-unknown-code $validate-code

a code that is not in the code system at all, validated against a filtered value set

exclude general

Tests for proper functioning of exclude

exclude-1 $expand

Test a simple exclude

exclude-2 $expand

Test a simple exclude combined with a filter

exclude-zero $expand

include and exclude the same code

exclude-all $expand

include and exclude all codes

exclude-combo $expand

exclude by value set

exclude-valueset $expand

exclude a whole value set (an exclude with only a valueSet), referenced by url

exclude-contained $expand

exclude a whole contained value set (an exclude with only a valueSet, referenced as #id)

include-combo $expand

include limit by value set

exclude-gender $expand

See https://github.com/HealthIntersections/FHIRsmith/issues/156

exclude-gender2 $expand

See https://github.com/HealthIntersections/FHIRsmith/issues/156

exclude-validate-cc-in-first $validate-code

Validate a CodeableConcept with a code that is in the value set, then one that the value set excludes: the result is true, and the display returned is that of the code in the value set

exclude-validate-cc-in-last $validate-code

Validate a CodeableConcept with a code that the value set excludes, then one that is in the value set: the result is true, and the display returned is that of the code in the value set, not of the excluded one

search general

Tests for proper functioning of text search. Note what we're not interested in the implementation of the text search itself, so we only test very obvious results. We're just interested in testing support for the parameter

search-all-yes $expand

Test a simple search

search-all-no $expand

Test a simple search that returns no results

search-filter-yes $expand

Test a simple search

search-filter-no $expand

Test a simple search that returns no results

search-enum-yes $expand

Test a simple search

search-enum-no $expand

Test a simple search that returns no results

search-all-de-yes $expand

A text filter matches displays and designations in one language: the first language the request asks for that the code system has, else the code system's own. With displayLanguage=de, a German designation matches

search-all-de-no-language $expand

A text filter matches displays and designations in one language: the first language the request asks for that the code system has, else the code system's own. With no language asked for, the code system's own (English) is searched, so the German designation does not match

search-enum-de-yes $expand

The same for a value set that lists the code: with displayLanguage=de, its German designation matches

search-filter-de-yes $expand

The same for a value set with a filter: with displayLanguage=de, the German designation matches (the children have none)

search-all-supplement-fr-yes $expand

A text filter searches the designations of supplements in use as well, in the language searched: with displayLanguage=fr, the French designation that the referenced language pack gives matches

search-all-supplement-fr-no-language $expand

With no language asked for, the code system's own language (English) is searched, so the language pack's French designation does not match

search-lang-supplement-display $expand

A text filter matches the displays a supplement in use gives, in the language searched: with displayLanguage=es, the Spanish displays of an unreferenced global language pack match, and the pack is reported as a used-supplement

search-lang-supplement-only $expand

A supplement whose text is what matched is a used-supplement even when the displays shown are not its own: the code matches on the global language pack's Spanish designation, its display is the code system's own Spanish designation (which takes precedence), and the pack is reported as a used-supplement because it decided what the expansion contains

search-lang-own $expand

The same code, matched on the code system's own Spanish designation: the global language pack contributes nothing to the match or the display, so reporting it as a used-supplement is optional

default-valueset-version general

Test the default-valueset-version parameter

direct-expand-one $expand

Test the actual value set directly - v1

direct-expand-two $expand

Test the actual value set directly - v2

indirect-expand-one $expand

Test the actual value set indirectly - v1

indirect-expand-two $expand

Test the actual value set indirectly - v2

indirect-expand-zero $expand

Test the actual value set indirectly - versionless

indirect-expand-zero-pinned $expand

Test the actual value set indirectly - versionless, and specify a version

indirect-expand-zero-pinned-wrong $expand

Test the actual value set indirectly - versionless, and specify a version that doesn't exist

indirect-validation-one $validate-code

Test the value set indirectly

indirect-validation-two $validate-code

Test the value set indirectly

indirect-validation-zero $validate-code

Test the value set indirectly

indirect-validation-zero-pinned $validate-code

Test the value set indirectly

indirect-validation-zero-pinned-wrong $validate-code

Test the value set indirectly

tx.fhir.org tx.fhir.org

These are tx.fhir.org specific tests. There's no expectation that other servers will pass these tests, and they are not executed by default. (other servers can, but they depend on other set up not controlled by the tests

snomed-validation-1 $cs-validate-code

to be provided

hgvs-expand-all $expand

Attempt to expand the whole HGVS code system: it has a grammar and cannot be iterated, so a not-supported OperationOutcome is expected

snomed-expand-active $expand

Test the inactive filter

snomed-expand-inactive $expand

Test the inactive filter

snomed-expand-inactive2 $expand

Test the inactive filter

snomed-expand-moduleid-1 $expand

Test ModuleId filter

snomed-expand-moduleid-2 $expand

Test ModuleId filter

snomed-expand-moduleid-3 $expand

Test ModuleId filter

snomed-expand-moduleid-4 $expand

Test ModuleId filter

snomed-expand-property-1 $expand

Test Property filter

snomed-expand-property-2 $expand

Test Property filter

snomed-validate-active-bad $validate-code

Test inactive filter

snomed-validate-active-good $validate-code

Test inactive filter

snomed-validate-inactive-bad $validate-code

Test inactive filter

snomed-validate-inactive-good $validate-code

Test inactive filter

snomed-validate-moduleid-bad $validate-code

Test moduleid filter

snomed-validate-moduleid-good $validate-code

Test moduleid filter

snomed-validate-property-bad $validate-code

Test Property filter

snomed-validate-property-good $validate-code

Test Property filter

snomed-translate $translate

Implicit Snomed Concept Map

loinc loinc

LOINC tests. These depend on the LOINC release (2.83) and the accessory files the server has loaded, and every request names version 2.83

loinc-lookup-code $lookup

$lookup of a LOINC term. The six axes are code properties whose value is the Part code; CLASS is a string property whose value is the class name (CHEM). A server may also give the Part code for the class as partCode (an informal extension to the property part)

loinc-lookup-classtype $lookup

CLASSTYPE 3 (Claims attachment): its value is the code, 3, with the description as a part, as for the other class types (see loinc-lookup-code)

loinc-lookup-part $lookup

to be provided

loinc-lookup-list $lookup

to be provided

loinc-lookup-answer $lookup

to be provided

loinc-lookup-part-mappings $lookup

A LOINC part's mappings to other code systems (PartRelatedCodeMapping) are Coding properties named for the map - sct, ncbi (PubChem), chebi - with the equivalence as a subproperty. Asked for by name here; they are also returned by default (see loinc-lookup-code and loinc-lookup-answer)

loinc-lookup-part-parent $lookup

A part's parents in the multi-axial hierarchy, each once. LP14635-4 Glucose is listed under LP31399-6 on two paths in ComponentHierarchyBySystem, but it has that parent once

loinc-lookup-part-languages $lookup

The LinguisticVariant files translate each term's axes (COMPONENT, PROPERTY, TIME_ASPCT, SYSTEM, SCALE_TYP, METHOD_TYP, CLASS). Those translations are designations of the Parts, with use PartName - for ko-KR and most of fr-CA they are all LOINC has. With loinc-lookup-code-languages, this checks that every LOINC 2.83 language variant is loaded and available through $lookup: LP7565-7 Saliva has a PartName in 19 of them

loinc-lookup-code-languages $lookup

The two language variants loinc-lookup-part-languages does not cover: 66878-0 Skin Ab [Titer] in Serum has LinguisticVariantDisplayName designations in ar-JO and de-AT

loinc-lookup-answer-race $lookup

An answer's external code from the answer list (ExtCodeSystem https://www.cdc.gov/phin) is reported in the CDC race and ethnicity system, urn:oid:2.16.840.1.113883.6.238, as the property race

loinc-validate-code $cs-validate-code

to be provided

loinc-validate-code-uz $cs-validate-code

to be provided

loinc-validate-discouraged-code $cs-validate-code

to be provided

loinc-validate-code-supp1 $cs-validate-code

LOINC supplement test - code in the supplement, but english

loinc-validate-code-supp2 $cs-validate-code

LOINC supplement test - code in the supplement, but german from the supplement

loinc-validate-part $cs-validate-code

to be provided

loinc-validate-list $cs-validate-code

to be provided

loinc-validate-answer $cs-validate-code

to be provided

loinc-validate-invalid $cs-validate-code

to be provided

loinc-expand-enum $expand

to be provided

loinc-expand-property $expand

Properties asked for with the property parameter are returned on each code in the expansion (and declared in expansion.property) - the same values $lookup returns

loinc-expand-compose-property $expand

The same, with the properties asked for by the value set (ValueSet.compose.property)

loinc-expand-search-de $expand

A text filter matches names in one language: with displayLanguage=de-DE, the German names (Glucose [Masse/Volumen] in Serum oder Plasma) are searched

loinc-expand-search-no-language $expand

With no language asked for, English is searched, so a word only in the German names matches nothing

loinc-expand-search-filter-de $expand

A text filter in German with a property filter (COMPONENT = Glucose): the codes with Liquor in their German name

loinc-expand-all $expand

to be provided

loinc-expand-all-limited $expand tx.fhir.org

tx.fhir.org's own page of this expansion, in its order: $expand does not define which codes a page holds. A total, if returned, must be 257266. See loinc-expand-all-limited-total for the test all servers run

loinc-expand-all-limited-total $expand

The size of the expansion: count=0, and total must be 257266. Which codes a page of it holds is up to the server (see loinc-expand-all-limited)

loinc-expand-enum-bad $expand

Expansion of a value set that enumerates valid codes and two invalid ones (LA4489-6X, LP111373-9X). The server may refuse to expand the value set (4xx), or expand it with just the valid codes, saying the include referred to invalid codes in an expansion-issue (200)

loinc-expand-enum-invalid $expand

Expansion of a value set that enumerates a valid code and a code that is not in LOINC, though its check digit is right (99999-5). The server may refuse to expand the value set (4xx), or expand it with just the valid code, saying the include referred to an invalid code in an expansion-issue (200)

loinc-expand-enum-invalid-check-digit $expand

Expansion of a value set that enumerates a valid code and a code whose check digit is wrong (99999-6). The server may refuse to expand the value set (4xx), or expand it with just the valid code, saying the include referred to an invalid code in an expansion-issue (200)

loinc-expand-isa-invalid $expand

Expansion of a value set that includes a valid code, and everything that is-a 99999-5 (a code that is not in LOINC, though its check digit is right). The server may refuse to expand the value set (4xx), or expand it with just the valid code, saying the filter referred to an invalid code in an expansion-issue (200)

loinc-expand-isa-invalid-check-digit $expand

Expansion of a value set that includes a valid code, and everything that is-a 99999-6 (a code whose check digit is wrong). The server may refuse to expand the value set (4xx), or expand it with just the valid code, saying the filter referred to an invalid code in an expansion-issue (200)

loinc-validate-enum-invalid $validate-code

$validate-code of an unknown code (99973-0) against a value set that is invalid: it lists a code that is not in the code system (99999-5). Not valid, and as well as the usual errors, an error saying that the value set is not valid, and why

loinc-validate-enum-invalid-check-digit $validate-code

$validate-code of an unknown code (99973-0) against a value set that is invalid: it lists a code that is not in the code system (99999-6). Not valid, and as well as the usual errors, an error saying that the value set is not valid, and why

loinc-validate-isa-invalid $validate-code

$validate-code of an unknown code (99973-0) against a value set that is invalid: it has an is-a filter on a code that is not in the code system (99999-5). Not valid, and as well as the usual errors, an error saying that the value set is not valid, and why

loinc-validate-isa-invalid-check-digit $validate-code

$validate-code of an unknown code (99973-0) against a value set that is invalid: it has an is-a filter on a code that is not in the code system (99999-6). Not valid, and as well as the usual errors, an error saying that the value set is not valid, and why

loinc-expand-status $expand tx.fhir.org

tx.fhir.org's own page of this expansion, in its order: $expand does not define which codes a page holds. A total, if returned, must be 2224. See loinc-expand-status-total for the test all servers run

loinc-expand-status-total $expand

The size of the expansion: count=0, and total must be 2224. Which codes a page of it holds is up to the server (see loinc-expand-status)

loinc-expand-parent $expand

to be provided

loinc-expand-class-regex $expand tx.fhir.org

tx.fhir.org's own page of this expansion, in its order: $expand does not define which codes a page holds. A total, if returned, must be 3754. See loinc-expand-class-regex-total for the test all servers run

loinc-expand-class-regex-total $expand

The size of the expansion: count=0, and total must be 3754. Which codes a page of it holds is up to the server (see loinc-expand-class-regex). The regex matches the whole class name, as every regex filter does: CYTO matches the class CYTO, not PANEL.HL7.CYTOGEN, and LABORDERS not LABORDERS.ONTOLOGY

loinc-expand-prop-component $expand

to be provided

loinc-expand-prop-method $expand

Deliberately the wrong axis: METHOD_TYP filtered by LP14635-4, which is a COMPONENT Part (Glucose), not a method, so nothing matches and the expansion is empty. loinc-expand-prop-method-part filters by a method Part

loinc-expand-prop-method-part $expand

METHOD_TYP filtered by the Part code for a method (LP6527-8 Spirometry)

loinc-expand-prop-component-str $expand

COMPONENT filtered by the component name (Glucose), the legacy form. The Part code is the correct filter value for the six LOINC axes (COMPONENT, PROPERTY, TIME_ASPCT, SYSTEM, SCALE_TYP, METHOD_TYP), but filtering by the name is so widespread in existing value sets that all servers are required to support it. Same codes as loinc-expand-prop-component, which filters by the Part code

loinc-expand-prop-order-obs $expand tx.fhir.org

tx.fhir.org's own page of this expansion, in its order: $expand does not define which codes a page holds. A total, if returned, must be 56304. See loinc-expand-prop-order-obs-total for the test all servers run

loinc-expand-prop-order-obs-total $expand

The size of the expansion: count=0, and total must be 56304. Which codes a page of it holds is up to the server (see loinc-expand-prop-order-obs)

loinc-validate-filter-order-obs-in-good $validate-code

ORDER_OBS in Order,Both - core's [property] in [string,string...] filter: a property value equal to one of the strings. 100017-3 is ORDER_OBS Order

loinc-validate-filter-order-obs-in-bad $validate-code

ORDER_OBS in Order,Both (see loinc-validate-filter-order-obs-in-good): 100000-9 is ORDER_OBS Observation, so not in the value set

loinc-expand-prop-order-obs-in-total $expand

ORDER_OBS in Order,Both: the size of the expansion (count=0) is the size of the union of ORDER_OBS = Order (5466 codes) and ORDER_OBS = Both (56304): 61770

loinc-expand-prop-order-obs-in-case-total $expand

ORDER_OBS in order,BOTH: the same codes as loinc-expand-prop-order-obs-in-total. LOINC property values are not case sensitive for comparison (THO's LOINC page, Case Sensitivity)

loinc-expand-concept-is-a $expand

is-a on the LOINC hierarchy includes the concept itself. The hierarchy is read from ComponentHierarchyBySystem path by path: a code is a descendant of the parts on its own PATH_TO_ROOT, and the children a part has under one parent are not inherited by its other parents (LP263671-2 Bacilliform bacteria is under both LP14082-9 Bacteria and LP30609-9, and only its children on the Bacteria path are in this expansion)

loinc-expand-implicit-part $expand

LOINC's implicit value set for a Multi-Axial Hierarchy part, http://loinc.org/vs/[partcode], which LOINC defines as ancestor = [partcode]: all the codes the part subsumes (terms and parts), not the part itself. LP100039-9 Iloperidone

loinc-expand-copyright $expand tx.fhir.org

tx.fhir.org's own page of this expansion, in its order: $expand does not define which codes a page holds. A total, if returned, must be 7355. See loinc-expand-copyright-total for the test all servers run

loinc-expand-copyright-total $expand

The size of the expansion: count=0, and total must be 7355. Which codes a page of it holds is up to the server (see loinc-expand-copyright)

loinc-expand-scale-type $expand tx.fhir.org

SCALE_TYP filtered by the scale name (DOC), the legacy form. The Part code is the correct filter value for the six LOINC axes (COMPONENT, PROPERTY, TIME_ASPCT, SYSTEM, SCALE_TYP, METHOD_TYP), but filtering by the name is so widespread in existing value sets that all servers are required to support it. The Part code form is tested by the -part twin of this test. tx.fhir.org's own page of this expansion, in its order: $expand does not define which codes a page holds. A total, if returned, must be 12569. See loinc-expand-scale-type-total for the test all servers run

loinc-expand-scale-type-total $expand

The size of the expansion: count=0, and total must be 12569. Which codes a page of it holds is up to the server (see loinc-expand-scale-type)

loinc-expand-scale-type-part $expand tx.fhir.org

SCALE_TYP filtered by the Part code for the scale (LP32888-7 Doc), the correct value for the LOINC axes. Same codes as loinc-expand-scale-type. tx.fhir.org's own page of this expansion, in its order: $expand does not define which codes a page holds. A total, if returned, must be 12569. See loinc-expand-scale-type-part-total for the test all servers run

loinc-expand-scale-type-part-total $expand

The size of the expansion: count=0, and total must be 12569. Which codes a page of it holds is up to the server (see loinc-expand-scale-type-part)

loinc-validate-enum-good $validate-code

to be provided

loinc-validate-enum-bad $validate-code

to be provided

loinc-validate-filter-prop-component-good $validate-code

to be provided

loinc-validate-filter-prop-component-bad $validate-code

to be provided

loinc-validate-filter-status-good $validate-code

to be provided

loinc-validate-filter-status-bad $validate-code

to be provided

loinc-validate-filter-class-regex-good $validate-code

to be provided

loinc-validate-filter-class-regex-bad $validate-code

to be provided

loinc-validate-filter-scale-type-good $validate-code

SCALE_TYP filtered by the scale name (DOC), the legacy form. The Part code is the correct filter value for the six LOINC axes (COMPONENT, PROPERTY, TIME_ASPCT, SYSTEM, SCALE_TYP, METHOD_TYP), but filtering by the name is so widespread in existing value sets that all servers are required to support it. The Part code form is tested by the -part twin of this test

loinc-validate-filter-scale-type-bad $validate-code

SCALE_TYP filtered by the scale name (DOC), the legacy form. The Part code is the correct filter value for the six LOINC axes (COMPONENT, PROPERTY, TIME_ASPCT, SYSTEM, SCALE_TYP, METHOD_TYP), but filtering by the name is so widespread in existing value sets that all servers are required to support it. The Part code form is tested by the -part twin of this test

loinc-validate-filter-scale-type-part-good $validate-code

SCALE_TYP filtered by the Part code (LP32888-7 Doc): a document is in the value set

loinc-validate-filter-scale-type-part-bad $validate-code

SCALE_TYP filtered by the Part code (LP32888-7 Doc): a quantitative term is not in the value set

loinc-expand-class-scale $expand tx.fhir.org

CLASS = PULM (the class name, which is the correct value: CLASS is a string property) together with SCALE_TYP = LP7753-9 (the Part code for Qn, the correct value for an axis). This is how the MII lung function value set mii-vs-lufu-lnc-observable is written. tx.fhir.org's own page of this expansion, in its order: $expand does not define which codes a page holds. A total, if returned, must be 825. See loinc-expand-class-scale-total for the test all servers run

loinc-expand-class-scale-total $expand

The size of the expansion: count=0, and total must be 825. Which codes a page of it holds is up to the server (see loinc-expand-class-scale)

loinc-expand-class-part-scale $expand tx.fhir.org

CLASS = LP7840-4 (the Part code for the class PULM) together with SCALE_TYP = LP7753-9. The class name is the correct value for CLASS, which is a string property (see loinc-expand-class-scale), but filtering CLASS by the Part code is so widespread in existing value sets (e.g. the MII lung function value set mii-vs-lufu-lnc-observable) that all servers are required to support it. Same codes as loinc-expand-class-scale. tx.fhir.org's own page of this expansion, in its order: $expand does not define which codes a page holds. A total, if returned, must be 825. See loinc-expand-class-part-scale-total for the test all servers run

loinc-expand-class-part-scale-total $expand

The size of the expansion: count=0, and total must be 825. Which codes a page of it holds is up to the server (see loinc-expand-class-part-scale)

loinc-validate-filter-class-scale-good $validate-code

A pulmonary quantitative term is in the CLASS = PULM, SCALE_TYP = LP7753-9 value set

loinc-validate-filter-class-scale-bad-scale $validate-code

A pulmonary term that is not quantitative is not in the CLASS = PULM, SCALE_TYP = LP7753-9 value set

loinc-validate-filter-class-scale-bad-class $validate-code

A quantitative term that is not pulmonary is not in the CLASS = PULM, SCALE_TYP = LP7753-9 value set

loinc-validate-filter-class-part-scale-good $validate-code

A pulmonary quantitative term is in the CLASS = LP7840-4, SCALE_TYP = LP7753-9 value set. Filtering CLASS by the Part code is not correct (CLASS is a string property), but it is so widespread in existing value sets that all servers are required to support it

loinc-expand-list-request-parameters $expand

to be provided

loinc-validate-list-good $validate-code

to be provided

loinc-validate-list-bad $validate-code

to be provided

loinc-expand-filter-list-request-parameters $expand tx.fhir.org

Expand LIST = LL361-7. The LIST filter is tx.fhir.org's own, and it only supports it for backwards compatibility: the defined filter for answer list membership is answers-for (see UP-645). Expanding answers-for with an answer list code is tested by loinc-expand-filter-answers-for1

loinc-validate-filter-list-type-good $validate-code tx.fhir.org

LA33-6 is in LIST = LL361-7. The LIST filter is tx.fhir.org's own, and it only supports it for backwards compatibility: the defined filter for answer list membership is answers-for (see UP-645, and the answers-for twin of this test, loinc-validate-filter-answers-for3-good).

loinc-validate-filter-list-bad $validate-code tx.fhir.org

100746-7 is not in LIST = LL361-7. The LIST filter is tx.fhir.org's own, and it only supports it for backwards compatibility: the defined filter for answer list membership is answers-for (see UP-645, and the answers-for twin of this test, loinc-validate-filter-answers-for3-bad).

loinc-expand-filter-dockind-request-parameters $expand tx.fhir.org

tx.fhir.org's own page of this expansion, in its order: $expand does not define which codes a page holds. A total, if returned, must be 3730. See loinc-expand-prop-dockind-total for the test all servers run

loinc-expand-prop-dockind-total $expand

The size of the expansion: count=0, and total must be 3730. Which codes a page of it holds is up to the server (see loinc-expand-filter-dockind-request-parameters)

loinc-validate-filter-dockind-type-good $validate-code

to be provided

loinc-validate-filter-dockind-bad $validate-code

to be provided

loinc-expand-filter-no-method $expand tx.fhir.org

LOINC terms with no method: METHOD_TYP exists false, restricted to LOINC terms by CLASSTYPE exists true. tx.fhir.org's own page of this expansion, in its order: $expand does not define which codes a page holds. A total, if returned, must be 50886. See loinc-expand-filter-no-method-total for the test all servers run

loinc-expand-filter-no-method-total $expand

The size of the expansion: count=0, and total must be 50886. Which codes a page of it holds is up to the server (see loinc-expand-filter-no-method)

loinc-validate-filter-no-method-good $validate-code

a LOINC term with no method is in the no-method value set

loinc-validate-filter-no-method-method-bad $validate-code

a LOINC term with a method is not in the no-method value set

loinc-validate-filter-no-method-part-bad $validate-code

a LOINC part has no method, but is excluded by the CLASSTYPE exists filter

loinc-validate-filter-classtype-good $validate-code

test classtype filter (numerical)

loinc-validate-filter-classtype-bad $validate-code

test classtype filter (numerical)

loinc-validate-filter-classtype-in-good-3 $validate-code

CLASSTYPE in 3,4 - core's [property] in [string,string...] filter: a property value equal to one of the strings. As for =, the numbers 1-4 stand for the CLASSTYPE names. 18719-5 is CLASSTYPE 3 (Claims attachment)

loinc-validate-filter-classtype-in-good-4 $validate-code

CLASSTYPE in 3,4 (see loinc-validate-filter-classtype-in-good-3): 100002-5 is CLASSTYPE 4 (Surveys)

loinc-validate-filter-classtype-in-bad $validate-code

CLASSTYPE in 3,4 (see loinc-validate-filter-classtype-in-good-3): 100019-9 is CLASSTYPE 1 (Laboratory class), so not in the value set

loinc-expand-filter-classtype-in-total $expand

CLASSTYPE in 3,4: the size of the expansion (count=0) is the size of the union of CLASSTYPE = 3 (1161 codes) and CLASSTYPE = 4 (12807): 13968

loinc-validate-filter-classtype-in-names-good $validate-code

CLASSTYPE in Claims attachment,Surveys - the same filter as loinc-validate-filter-classtype-in-good-3, with the CLASSTYPE names instead of their numbers

loinc-expand-filter-classtype-in-names-total $expand

CLASSTYPE in Claims attachment,Surveys: the same codes as CLASSTYPE in 3,4 (loinc-expand-filter-classtype-in-total), 13968

loinc-expand-filter-answers-for1 $expand

Test answers-for filters with LL code

loinc-expand-filter-answers-for2 $expand

Test answers-for filters with normal code

loinc-validate-filter-answers-for3-good $validate-code

answers-for with an answer list code (LL361-7): an answer in the list (LA33-6) is in the value set

loinc-validate-filter-answers-for3-bad $validate-code

answers-for with an answer list code (LL361-7): a code that isn't an answer in the list (100746-7) is not in the value set

loinc-expand-filter-answer-list $expand

answer-list = an answer code (LA9040-2 Ongoing): the answer lists the answer is in (LL451-6 and LL6136-7) - the inverse of answers-for

loinc-validate-filter-answer-list-good $validate-code

answer-list = LA9040-2: an answer list the answer is in (LL6136-7) is in the value set

loinc-validate-filter-answer-list-bad $validate-code

answer-list = LA9040-2: an answer list the answer is not in (LL361-7) is not in the value set

loinc-validate-filter-answers-for4-good $validate-code

answers-for an answer list (LL1746-8): an answer in the list that many other lists share (LA14331-5, Both) is in the value set

loinc-validate-filter-answers-for4-bad $validate-code

answers-for an answer list (LL1746-8): an answer that isn't in the list (LA33-6) is not in the value set

loinc-validate-concept-is-a-good $validate-code

concept is-a LP14082-9 (Bacteria): a code below the part (10352-3) is in the value set

loinc-validate-concept-is-a-self $validate-code

concept is-a LP14082-9 (Bacteria): the part itself is in the value set

loinc-validate-concept-is-a-bad $validate-code

concept is-a LP14082-9 (Bacteria): a code that is not below the part (2345-7) is not in the value set

loinc-validate-filter-copyright-good $validate-code

copyright = 3rdParty: a code with third party copyright (100017-3) is in the value set

loinc-validate-filter-copyright-bad $validate-code

copyright = 3rdParty: a code that is LOINC's own (8302-2) is not in the value set

loinc-subsumes-equivalent $subsumes

A LOINC code is equivalent to itself

loinc-subsumes-parent $subsumes

A LOINC part subsumes a code beneath it in the multiaxial hierarchy

loinc-subsumes-child $subsumes

the mirror of loinc-subsumes-parent

loinc-subsumes-unrelated $subsumes

Two unrelated LOINC codes

loinc-subsumes-unknown-code $subsumes

codeA is not a LOINC code

loinc-translate-part-sct $translate

Translate a LOINC part to SNOMED CT by naming the target system: the implicit map http://loinc.org/cm/sct (from PartRelatedCodeMapping) is found

loinc-translate-sct-part $translate

Translate a SNOMED CT concept to LOINC by naming the target system: the same map, used the other way. Three parts map to 409822003; the one LOINC says the SNOMED CT concept is narrower than comes back as source-is-narrower-than-target

loinc-translate-part-sct-url $translate

Translate a LOINC part to SNOMED CT by naming the map, http://loinc.org/cm/sct. LOINC says the SNOMED CT concept is narrower than the part, so the source is broader than the target

loinc-translate-code-mdc $translate

Translate a LOINC code to ISO/IEEE 11073 MDC with the map from the LOINC/IEEE medical device code mapping table, found by the target system. The MDC codes are narrower than the LOINC code, so the source is broader than the target

snomed snomed

This snomed tests are based on the testing subset in the tx-ecosystem IG github repo (see /tx-source)

snomed-inactive-display-lenient $cs-validate-code

check that inactive displays are validated properly

snomed-inactive-display-notlenient $cs-validate-code

check that inactive displays are validated properly

snomed-isa-in $validate-code

check that codes are validated properly (is-a heirachy) - in the value set

snomed-isa-out $validate-code

check that codes are validated properly (is-a heirachy) - not in the value set

snomed-expand-inactive $expand

check that inactive concepts and displays are expanded properly

snomed-expand-enum-invalid $expand

Expansion of a value set that enumerates a valid code and a code that is not in the edition, though its check digit is right (999999006). The server may refuse to expand the value set (4xx), or expand it with just the valid code, saying the include referred to an invalid code in an expansion-issue (200)

snomed-expand-enum-invalid-check-digit $expand

Expansion of a value set that enumerates a valid code and a code whose check digit is wrong (999999007). The server may refuse to expand the value set (4xx), or expand it with just the valid code, saying the include referred to an invalid code in an expansion-issue (200)

snomed-expand-isa-invalid $expand

Expansion of a value set that includes a valid code, and everything that is-a 999999006 (a code that is not in the edition, though its check digit is right). The server may refuse to expand the value set (4xx), or expand it with just the valid code, saying the filter referred to an invalid code in an expansion-issue (200)

snomed-expand-isa-invalid-check-digit $expand

Expansion of a value set that includes a valid code, and everything that is-a 999999007 (a code whose check digit is wrong). The server may refuse to expand the value set (4xx), or expand it with just the valid code, saying the filter referred to an invalid code in an expansion-issue (200)

snomed-validate-enum-invalid $validate-code

$validate-code of an unknown code (999998003) against a value set that is invalid: it lists a code that is not in the code system (999999006). Not valid, and as well as the usual errors, an error saying that the value set is not valid, and why

snomed-validate-enum-invalid-check-digit $validate-code

$validate-code of an unknown code (999998003) against a value set that is invalid: it lists a code that is not in the code system (999999007). Not valid, and as well as the usual errors, an error saying that the value set is not valid, and why

snomed-validate-isa-invalid $validate-code

$validate-code of an unknown code (999998003) against a value set that is invalid: it has an is-a filter on a code that is not in the code system (999999006). Not valid, and as well as the usual errors, an error saying that the value set is not valid, and why

snomed-validate-isa-invalid-check-digit $validate-code

$validate-code of an unknown code (999998003) against a value set that is invalid: it has an is-a filter on a code that is not in the code system (999999007). Not valid, and as well as the usual errors, an error saying that the value set is not valid, and why

snomed-expand-isa $expand

check that a set of concepts and displays are expanded properly (is-a)

snomed-expand-include-exclude $expand

a compose with two is-a includes and an is-a exclude: the excluded subtree is removed. Servers that combine the parts into one ECL expression must bracket them

snomed-expand-include-exclude-multi $expand

a compose with two is-a includes and two is-a excludes, one of which removes a whole include

snomed-expand-count-all $expand

Smoke test: total concept count for the loaded SNOMED edition subset must be 2206.

snomed-expand-too-big $expand

return too many codes at once - fails

lookup $lookup

Tests the $lookup operation for a simple SCT concept

lookup-pc $lookup

Tests the $lookup operation for a complex SCT expression

lookup-pc-unbracketed $lookup

An attribute value that is itself refined must be bracketed in the compositional grammar (405813007=(85562004:272741003=24028007)); without the brackets the expression is invalid, and $lookup fails

validate-code-pc-good $cs-validate-code

Tests the $validate-code operation for a complex SCT expression

validate-code-pc-bad1 $cs-validate-code

Tests the $validate-code operation for a complex SCT expression with a wrong qualifier code

validate-code-pc-bad2 $cs-validate-code

Tests the $validate-code operation for a complex SCT expression with a wrong qualifier code - the codes are valid but they are reversed

validate-code-pc-nested-good $cs-validate-code

Tests the $validate-code operation for an expression whose attribute value is itself refined - right hand as the procedure site

validate-code-pc-unbracketed $cs-validate-code

As validate-code-pc-nested-good, but without the brackets the compositional grammar requires around a refined attribute value - so it is not a valid expression

validate-code-pc-mrcm-lateralizable $cs-validate-code

The concept model does not allow laterality on a body structure that is not in the lateralizable body structure reference set

validate-code-pc-mrcm-domain $cs-validate-code

The concept model does not allow an attribute outside its domain - finding site on a body structure

validate-code-pc-mrcm-domain-finding $cs-validate-code

An attribute with more than one domain in the concept model is valid in any of them - due to on a clinical finding (due to is also valid on an event)

validate-code-pc-mrcm-domain-event $cs-validate-code

An attribute with more than one domain in the concept model is valid in any of them - due to on an event (due to is also valid on a clinical finding)

validate-code-pc-mrcm-domain-multi $cs-validate-code

The concept model does not allow an attribute outside all of its domains - due to on a procedure, when it is only valid on a clinical finding or an event

validate-code-pc-mrcm-range $cs-validate-code

The concept model does not allow a value outside the attribute's range - a body structure as the value of laterality

validate-code-pc-mrcm-cardinality $cs-validate-code

The concept model does not allow an attribute more times than its cardinality - laterality is 0..1

validate-code-pc-mrcm-grouped $cs-validate-code

The concept model does not allow an ungrouped attribute inside a relationship group - laterality is ungrouped

validate-code-pc-concrete-good $cs-validate-code

Tests the $validate-code operation for an expression with a concrete value

validate-code-pc-scg-no-comma $cs-validate-code

The comma before an attribute group is optional in the compositional grammar, so an attribute set followed directly by a group has to be accepted - it normalises to the form with the comma

validate-code-pc-scg-comma $cs-validate-code

The same expression written with the optional comma is already the normal form, so it validates with no issues

validate-code-pc-mrcm-concrete-range $cs-validate-code

The concept model does not allow a concrete value outside the attribute's range - the value must be greater than zero

validate-code-pc-mrcm-concrete-int $cs-validate-code

The concept model does not allow a decimal where the attribute's range is an integer

validate-code-pc-mrcm-concrete-wanted $cs-validate-code

The concept model does not allow a concept where the attribute's range is a concrete value

validate-code-pc-mrcm-concept-wanted $cs-validate-code

The concept model does not allow a concrete value where the attribute's range is a concept

validate-code-pc-none $validate-code

Checks that a valid expression is not allowed when expressions are not allowed

validate-code-pc-list $validate-code

Checks that a valid expression is allowed when expressions are listed

validate-code-pc-list-bad $validate-code

Checks that a valid expression is not allowed just because it's primacy code is listed

validate-code-pc-filter $validate-code

Checks that a valid expression is allowed when expressions are allowed

expand-pc-none $expand

Expands no expresssions allowed - check settings

expand-pc-list $expand

Checks that a valid expression is not allowed just because it's primacy code is listed

expand-pc-filter $expand

Checks that a valid expression is allowed when expressions are allowed

validate-code-implied-1 $validate-code

Check that implied value sets work (isa)

validate-code-implied-1b $validate-code

Check that implied value sets work (bad isa)

validate-code-implied-2 $validate-code

Check that implied value sets work (refset)

validate-code-implied-2b $validate-code

Check that implied value sets work (refset)

subsumes-simple $subsumes

A code is subsumed by its stated parent

subsumes-parent $subsumes

A code subsumes its stated child

subsumes-equivalent $subsumes

A code is equivalent to itself

subsumes-transitive $subsumes

Subsumption is transitive - a code subsumes a distant descendant

subsumes-siblings $subsumes

Two sibling codes do not subsume each other

subsumes-disjoint $subsumes

Two codes in different top level hierarchies do not subsume each other

subsumes-coding $subsumes

Subsumption using codingA/codingB instead of system + codeA/codeB

subsumes-unknown-code-a $subsumes

codeA is a well formed SNOMED code that is not in this edition

subsumes-unknown-code-b $subsumes

codeB is a well formed SNOMED code that is not in this edition

subsumes-invalid-code $subsumes

codeA is not a valid SNOMED code at all

subsumes-bad-version $subsumes

the version names a SNOMED edition the server does not have

subsumes-bad-system $subsumes

the system is not a code system the server knows

subsumes-expr-refined-vs-parent $subsumes

a refined expression is still subsumed by an ancestor of its focus concept

subsumes-expr-parent-vs-refined $subsumes

the mirror of subsumes-expr-refined-vs-parent

subsumes-expr-vs-focus $subsumes

a refined expression is subsumed by its own focus concept

subsumes-expr-attr-value $subsumes

same attribute, and the value in A subsumes the value in B

subsumes-expr-attr-value-reverse $subsumes

the mirror of subsumes-expr-attr-value

subsumes-expr-attr-unrelated $subsumes

same attribute, unrelated values: structure finds nothing, which does not establish that nothing is there

subsumes-expr-extra-attribute $subsumes

B carries every attribute A does, and one more

subsumes-expr-different-attributes $subsumes

each expression refines an attribute the other does not: no structural relationship either way, and no proof that none exists

subsumes-expr-primitive-focus $subsumes

an expression against a PRIMITIVE concept whose entailed attributes satisfy it - the attributes are necessary conditions, so they count

subsumes-expr-normal-form $subsumes

a concept against its own long normal form written out

subsumes-expr-redundant-refinement $subsumes

a refinement that restates the concept's own definition

subsumes-expr-grouped-ungrouped $subsumes

the same attribute grouped and ungrouped: the MRCM marks |Finding site| as grouped, so the ungrouped spelling is Close To User Form and is transformed to the self-grouped classifiable form (SNOMED postcoordination guide) - the two are equivalent

subsumes-expr-ungrouped-morphology $subsumes

the grouping transformation is not specific to |Finding site|: |Associated morphology| is grouped too, so the ungrouped refinement is self-grouped and the expression is subsumed by its focus

subsumes-expr-ungrouped-laterality $subsumes

|Laterality| is ungrouped in the MRCM, so writing it outside a group is correct and subsumption proceeds

subsumes-expr-with-terms $subsumes

the same expression with and without terms

subsumes-expr-conjunction $subsumes

a conjunction of a concept with its own ancestor

subsumes-expr-precoordinated-match $subsumes

an expression that means exactly the same as a precoordinated concept

subsumes-expr-subsumes-precoordinated $subsumes

a post-coordinated expression subsuming a precoordinated concept

snomed-translate-edition-intl $translate

Translate from the test edition to the International Edition with no ConceptMap: an International concept translates to itself

snomed-translate-edition-module $translate

Translate from the test edition to the International Edition with no ConceptMap: the module concept has no inferred IS A in the extract (only an OWL axiom), so it has no International ancestor at all

snomed-translate-edition-ungrouped $translate

Translate from the test edition to the International Edition with no ConceptMap: fully defined extension concept with one ungrouped attribute: the expression

snomed-translate-edition-grouped $translate

Translate from the test edition to the International Edition with no ConceptMap: fully defined extension concept with role groups: the normal form expression

snomed-translate-edition-equivalent $translate

Translate from the test edition to the International Edition with no ConceptMap: fully defined extension concept whose definition is an existing International concept: that concept, not an expression

snomed-translate-edition-primitive $translate

Translate from the test edition to the International Edition with no ConceptMap: primitive extension concept: the closest International ancestor, and the source is narrower

snomed-translate-edition-toplevel $translate

Translate from the test edition to the International Edition with no ConceptMap: primitive extension concept directly under a top-level hierarchy: no useful translation

snomed-translate-edition-inactive-none $translate

Translate from the test edition to the International Edition with no ConceptMap: inactive extension concept with no historical association: nothing to translate to

snomed-translate-edition-inactive-replaced $translate

Translate from the test edition to the International Edition with no ConceptMap: inactive extension concept REPLACED BY an International concept: that concept

snomed-lookup-loinc $lookup

LOINC Extension: $lookup asking for the loinc property returns the LOINC code; effectiveTime, module, parent and child are optional, since they were not asked for

snomed-lookup-loinc-inactive $lookup

LOINC Extension: an inactive LOINC Extension concept still has its LOINC code

snomed-lookup-loinc-none $lookup

LOINC Extension: a concept with no LOINC code has no loinc property

snomed-lookup-loinc-default $lookup

LOINC Extension: with no properties asked for, $lookup includes the LOINC code (mappings are returned by default)

snomed-expand-loinc $expand

LOINC Extension: filter mapped:30051010000102 exists true - every concept with a LOINC code (12, one inactive)

snomed-expand-loinc-isa $expand

LOINC Extension: concepts under Renal function that have a LOINC code

snomed-expand-loinc-isa-none $expand

LOINC Extension: concepts under Renal function that do not have a LOINC code

snomed-translate-loinc $translate

LOINC Extension: translate a SNOMED CT concept to its LOINC code with the implicit map ?fhir_cm=11010000107

snomed-translate-loinc-none $translate

LOINC Extension: a SNOMED CT concept with no LOINC code has no translation

snomed-translate-loinc-reverse $translate

LOINC Extension: translate a LOINC code to its SNOMED CT concept with the implicit map ?fhir_cm=11010000107

snomed-translate-loinc-reverse-none $translate

LOINC Extension: a LOINC code with no concept in the edition has no translation

snomed-translate-loinc-system $translate

LOINC Extension: translate a SNOMED CT concept to LOINC by naming the target system (http://loinc.org) rather than the map: the implicit map ?fhir_cm=11010000107 is found

snomed-translate-loinc-system-reverse $translate

LOINC Extension: translate a LOINC code to SNOMED CT by naming the target system (the edition, as system|version) rather than the map: the implicit map ?fhir_cm=11010000107 is found

snomed-expand-property-inactive-rel $expand

Inactive relationships are ignored: a property filter (363698007 = Kidney structure) does not match 50325005, whose only Kidney finding site row is inactive

snomed-lookup-inactive-rel $lookup

Inactive relationships are ignored: $lookup of 50325005 lists neither the inactive finding site (Kidney structure) nor the inactive parent (Hepatorenal syndrome)

snomed-lookup-inactive-isa-child $lookup

Inactive relationships are ignored: $lookup of Hepatorenal syndrome does not list 50325005, whose is-a row to it is inactive, as a child

snomed-lookup-concrete $lookup

$lookup returns concrete values as properties, typed by value: a string, a boolean, decimals (the strength attributes are dec() in the MRCM, so #4000 is a decimal there), and an integer (int() in the MRCM)

snomed-lookup-all-properties $lookup

$lookup with property=* returns every property the SNOMED CT on FHIR page defines - including moduleId, sufficientlyDefined and semanticTag - except the normal forms, which have to be asked for by name

snomed-lookup-normal-form $lookup

$lookup returns the normal form when it is asked for by name (here normalFormTerse, without terms)

snomed-validate-implied-refset-map $validate-code

The implicit value set ?fhir_vs=refset/ can name a map reference set: a concept mapped by the test edition's extended map is in it

snomed-expand-implicit-ecl $expand

The implicit value set ?fhir_vs=ecl/ (the ECL URL-encoded, as the SNOMED CT on FHIR page has it): << 16763008 |Hemorrhage of liver| gives the same codes as an inline is-a compose

snomed-expand-implicit-edition $expand

The implicit value set named by edition, with no version and no system-version: the latest version of the test edition the server has, here its only one

snomed-expand-implicit-version $expand

The implicit value set named by edition and version: that version of the test edition

snomed-expand-implicit-system-version $expand

The generic implicit value set form (http://snomed.info/sct?fhir_vs=...) is drawn from the edition system-version asks for: 1000071000003108 is a test edition extension concept, which a server's default edition does not have

snomed-expand-isa-inactive-isa $expand

Inactive relationships are ignored: an is-a filter on Hepatorenal syndrome does not include 50325005, whose is-a row to it is inactive

subsumes-inactive-isa $subsumes

Inactive relationships are ignored: Hepatorenal syndrome does not subsume 50325005, whose is-a row to it is inactive

snomed-expand-concept-in $expand

concept in with three plain codes: in means any of the listed codes, so all three are in the expansion

snomed-expand-property $expand

Properties asked for with the property parameter are returned on each code in the expansion (and declared in expansion.property): the module, sufficientlyDefined and a defining relationship (finding site), which repeats on 51292008 and is absent on 10200004

snomed-validate-concept-in $validate-code

concept in with three plain codes: one of the listed codes is in the value set

snomed-expand-code-in $expand

code in with three plain codes: code is the same filter property as concept (value sets in production use it), so all three are in the expansion

snomed-validate-code-in $validate-code

code in with three plain codes: code is the same filter property as concept, so one of the listed codes is in the value set

snomed-expand-descendent-leaf $expand

descendent-leaf (R5): only the descendants of Hemorrhage of liver that have no children; neither the concept itself nor the descendants with children

snomed-expand-is-not-a $expand

is-not-a (R5): is-a Hemorrhage of liver, less Traumatic hemorrhage of liver and its descendants

snomed-expand-display-regex $expand

display regex: matches every active description in one language (here the edition default, English), the whole term, case-sensitively

snomed-validate-display-regex $validate-code

display regex: a concept with a matching English description is in the value set

snomed-expand-display-regex-nl $expand

display regex in another language: with displayLanguage nl, the Dutch descriptions are matched (the test edition's TEST1000003 Dutch descriptions and language reference set), and the displays are the Dutch preferred terms

sct-ec snomed

Extension-codes supplements for the SNOMED CT test edition: a supplement gives some post-coordinated expressions human displays. In the snomed mode, and a suite of its own, since its global supplement would change the snomed suite's other tests

ec-sct-lookup-global $lookup

SNOMED CT: $lookup of a post-coordinated expression that a global extension-codes supplement gives a display: it has the supplement's display

ec-sct-lookup-local-referenced $lookup

$lookup of a post-coordinated expression that an extension-codes supplement that is not global gives a display, when the supplement is referenced: it has the supplement's display

ec-sct-lookup-local-unreferenced $lookup

The same when the supplement is not referenced: the display is the one generated from the expression

ec-sct-validate-global $cs-validate-code

$validate-code of a post-coordinated expression that a global extension-codes supplement gives a display, with no display: the display is the supplement's

ec-sct-validate-global-display $cs-validate-code

The same code with the supplement's display: valid

ec-sct-validate-global-generated-display $cs-validate-code

The same code with the generated display: still valid, though the supplement's display is the one returned

ec-sct-validate-global-wrong-display $cs-validate-code

The same code with a different display: an error, as for a display the code system gives

ec-sct-validate-global-wrong-display-lenient $cs-validate-code

The same, with lenient-display-validation: a warning

ec-sct-validate-local-referenced $cs-validate-code

$validate-code of a post-coordinated expression that a referenced extension-codes supplement (not global) gives a display, with no display: the display is the supplement's

ec-sct-validate-local-referenced-wrong-display $cs-validate-code

The same code with a different display: valid, with a warning

ec-sct-validate-local-unreferenced $cs-validate-code

The same code with the supplement's display, when the supplement is not referenced: the supplement is not used, so its display is not a display of the code

ec-sct-expand $expand

$expand of a value set that lists post-coordinated expressions without displays: those the global supplement gives displays get them, the others get their generated displays

ec-sct-expand-referenced $expand

The same, with the supplement that is not global referenced: all four get the supplements' displays

sct-ecl snomed

SNOMED CT ECL tests (expand + validate-code), split out of the snomed suite for manageability. Files live in sct/ecl/.

snomed-validate-ecl-descendents-code-in $validate-code

validate-code against ECL "descendents": a code that IS in the set

snomed-validate-ecl-descendents-code-out $validate-code

validate-code against ECL "descendents": a code that is NOT in the set

snomed-validate-ecl-descendents-expr-in $validate-code

validate-code against ECL "descendents": a post-coordinated expression that IS in the set

snomed-validate-ecl-descendents-expr-out $validate-code

validate-code against ECL "descendents": a post-coordinated expression that is NOT in the set

snomed-validate-ecl-descOrSelf-code-in $validate-code

validate-code against ECL "descOrSelf": a code that IS in the set

snomed-validate-ecl-descOrSelf-code-out $validate-code

validate-code against ECL "descOrSelf": a code that is NOT in the set

snomed-validate-ecl-descOrSelf-expr-in $validate-code

validate-code against ECL "descOrSelf": a post-coordinated expression that IS in the set

snomed-validate-ecl-descOrSelf-expr-out $validate-code

validate-code against ECL "descOrSelf": a post-coordinated expression that is NOT in the set

snomed-validate-ecl-children-code-in $validate-code

validate-code against ECL "children": a code that IS in the set

snomed-validate-ecl-children-code-out $validate-code

validate-code against ECL "children": a code that is NOT in the set

snomed-validate-ecl-children-expr-in $validate-code

validate-code against ECL "children": a post-coordinated expression that IS in the set

snomed-validate-ecl-children-expr-out $validate-code

validate-code against ECL "children": a post-coordinated expression that is NOT in the set

snomed-validate-ecl-childrenOrSelf-code-in $validate-code

validate-code against ECL "childrenOrSelf": a code that IS in the set

snomed-validate-ecl-childrenOrSelf-code-out $validate-code

validate-code against ECL "childrenOrSelf": a code that is NOT in the set

snomed-validate-ecl-childrenOrSelf-expr-in $validate-code

validate-code against ECL "childrenOrSelf": a post-coordinated expression that IS in the set

snomed-validate-ecl-childrenOrSelf-expr-out $validate-code

validate-code against ECL "childrenOrSelf": a post-coordinated expression that is NOT in the set

snomed-validate-ecl-ancestors-code-in $validate-code

validate-code against ECL "ancestors": a code that IS in the set

snomed-validate-ecl-ancestors-code-out $validate-code

validate-code against ECL "ancestors": a code that is NOT in the set

snomed-validate-ecl-ancestors-expr-out $validate-code

validate-code against ECL "ancestors": a post-coordinated expression that is NOT in the set

snomed-validate-ecl-ancOrSelf-code-in $validate-code

validate-code against ECL "ancOrSelf": a code that IS in the set

snomed-validate-ecl-ancOrSelf-code-out $validate-code

validate-code against ECL "ancOrSelf": a code that is NOT in the set

snomed-validate-ecl-ancOrSelf-expr-out $validate-code

validate-code against ECL "ancOrSelf": a post-coordinated expression that is NOT in the set

snomed-validate-ecl-parents-code-in $validate-code

validate-code against ECL "parents": a code that IS in the set

snomed-validate-ecl-parents-code-out $validate-code

validate-code against ECL "parents": a code that is NOT in the set

snomed-validate-ecl-parents-expr-out $validate-code

validate-code against ECL "parents": a post-coordinated expression that is NOT in the set

snomed-validate-ecl-parentsOrSelf-code-in $validate-code

validate-code against ECL "parentsOrSelf": a code that IS in the set

snomed-validate-ecl-parentsOrSelf-code-out $validate-code

validate-code against ECL "parentsOrSelf": a code that is NOT in the set

snomed-validate-ecl-parentsOrSelf-expr-out $validate-code

validate-code against ECL "parentsOrSelf": a post-coordinated expression that is NOT in the set

snomed-validate-ecl-refinement-simple-code-in $validate-code

validate-code against ECL "refinement-simple": a code that IS in the set

snomed-validate-ecl-refinement-simple-code-out $validate-code

validate-code against ECL "refinement-simple": a code that is NOT in the set

snomed-validate-ecl-refinement-simple-expr-in $validate-code

validate-code against ECL "refinement-simple": a post-coordinated expression that IS in the set

snomed-validate-ecl-refinement-simple-expr-out $validate-code

validate-code against ECL "refinement-simple": a post-coordinated expression that is NOT in the set

snomed-validate-ecl-refinement-group-code-out $validate-code

validate-code against ECL "refinement-group": a code that is NOT in the set

snomed-validate-ecl-refinement-group-expr-in $validate-code

validate-code against ECL "refinement-group": a post-coordinated expression that IS in the set

snomed-validate-ecl-refinement-group-expr-out $validate-code

validate-code against ECL "refinement-group": a post-coordinated expression that is NOT in the set

snomed-validate-ecl-refinement-morphology-code-in $validate-code

validate-code against ECL "refinement-morphology": a code that IS in the set

snomed-validate-ecl-refinement-morphology-code-out $validate-code

validate-code against ECL "refinement-morphology": a code that is NOT in the set

snomed-validate-ecl-refinement-morphology-expr-in $validate-code

validate-code against ECL "refinement-morphology": a post-coordinated expression that IS in the set

snomed-validate-ecl-refinement-morphology-expr-out $validate-code

validate-code against ECL "refinement-morphology": a post-coordinated expression that is NOT in the set

snomed-validate-ecl-refinement-wildcard-code-in $validate-code

validate-code against ECL "refinement-wildcard": a code that IS in the set

snomed-validate-ecl-refinement-wildcard-code-out $validate-code

validate-code against ECL "refinement-wildcard": a code that is NOT in the set

snomed-validate-ecl-refinement-wildcard-expr-in $validate-code

validate-code against ECL "refinement-wildcard": a post-coordinated expression that IS in the set

snomed-validate-ecl-refinement-wildcard-expr-out $validate-code

validate-code against ECL "refinement-wildcard": a post-coordinated expression that is NOT in the set

snomed-validate-ecl-refinement-cardinality-code-in $validate-code

validate-code against ECL "refinement-cardinality": a code that IS in the set

snomed-validate-ecl-refinement-cardinality-code-out $validate-code

validate-code against ECL "refinement-cardinality": a code that is NOT in the set

snomed-validate-ecl-refinement-cardinality-expr-in $validate-code

validate-code against ECL "refinement-cardinality": a post-coordinated expression that IS in the set

snomed-validate-ecl-refinement-cardinality-expr-out $validate-code

validate-code against ECL "refinement-cardinality": a post-coordinated expression that is NOT in the set

snomed-validate-ecl-refinement-cardinality-grouped-code-in $validate-code

validate-code against ECL "refinement-cardinality-grouped": a code that IS in the set

snomed-validate-ecl-refinement-cardinality-grouped-code-out $validate-code

validate-code against ECL "refinement-cardinality-grouped": a code that is NOT in the set

snomed-validate-ecl-refinement-cardinality-grouped-expr-in $validate-code

validate-code against ECL "refinement-cardinality-grouped": a post-coordinated expression that IS in the set

snomed-validate-ecl-refinement-cardinality-grouped-expr-out $validate-code

validate-code against ECL "refinement-cardinality-grouped": a post-coordinated expression that is NOT in the set

snomed-validate-ecl-refinement-cardinality-rolegroup-code-in $validate-code

validate-code against ECL "refinement-cardinality-rolegroup": a code that IS in the set

snomed-validate-ecl-refinement-cardinality-rolegroup-code-out $validate-code

validate-code against ECL "refinement-cardinality-rolegroup": a code that is NOT in the set

snomed-validate-ecl-refinement-cardinality-rolegroup-expr-in $validate-code

validate-code against ECL "refinement-cardinality-rolegroup": a post-coordinated expression that IS in the set

snomed-validate-ecl-refinement-cardinality-rolegroup-expr-out $validate-code

validate-code against ECL "refinement-cardinality-rolegroup": a post-coordinated expression that is NOT in the set

snomed-validate-ecl-memberOf-refset-code-in $validate-code

validate-code against ECL "memberOf-refset": a code that IS in the set

snomed-validate-ecl-memberOf-refset-code-out $validate-code

validate-code against ECL "memberOf-refset": a code that is NOT in the set

snomed-validate-ecl-memberOf-refset-expr-out $validate-code

validate-code against ECL "memberOf-refset": a post-coordinated expression that is NOT in the set

snomed-validate-ecl-minus-code-in $validate-code

validate-code against ECL "minus": a code that IS in the set

snomed-validate-ecl-minus-code-out $validate-code

validate-code against ECL "minus": a code that is NOT in the set

snomed-validate-ecl-minus-expr-in $validate-code

validate-code against ECL "minus": a post-coordinated expression that IS in the set

snomed-validate-ecl-minus-expr-out $validate-code

validate-code against ECL "minus": a post-coordinated expression that is NOT in the set

snomed-validate-ecl-wildcard-code-in $validate-code

validate-code against ECL "wildcard": a code that IS in the set

snomed-validate-ecl-wildcard-expr-in $validate-code

validate-code against ECL "wildcard": a post-coordinated expression that IS in the set

snomed-validate-ecl-wildcard-minus-code-in $validate-code

validate-code against ECL "wildcard-minus": a code that IS in the set

snomed-validate-ecl-wildcard-minus-code-out $validate-code

validate-code against ECL "wildcard-minus": a code that is NOT in the set

snomed-validate-ecl-wildcard-minus-expr-in $validate-code

validate-code against ECL "wildcard-minus": a post-coordinated expression that IS in the set

snomed-validate-ecl-wildcard-minus-expr-out $validate-code

validate-code against ECL "wildcard-minus": a post-coordinated expression that is NOT in the set

snomed-expand-ecl-descOrSelf $expand

check that a set of concepts and displays are expanded properly (ecl descendent-or-self)

snomed-expand-ecl-descendents $expand

check that a set of concepts and displays are expanded properly (ecl descendent)

snomed-expand-ecl-ancestors $expand

check that a set of concepts and displays are expanded properly (ecl ancestor)

snomed-expand-ecl-ancOrSelf $expand

check that a set of concepts and displays are expanded properly (ecl ancestor-or-self)

snomed-expand-ecl-childrenOrSelf $expand

check that a set of concepts and displays are expanded properly (ecl descendent-or-self)

snomed-expand-ecl-children $expand

check that a set of concepts and displays are expanded properly (ecl descendent)

snomed-expand-ecl-parents $expand

check that a set of concepts and displays are expanded properly (ecl ancestor)

snomed-expand-ecl-parentsOrSelf $expand

check that a set of concepts and displays are expanded properly (ecl ancestor-or-self)

snomed-expand-ecl-wildcard $expand

All active concepts in the subset (wildcard).

snomed-expand-ecl-memberOf-refset $expand

Members of the REPLACED-BY association reference set.

snomed-expand-ecl-memberOf-nonRefset $expand

Negative case: ^ applied to a concept that is not a reference set should error.

snomed-expand-ecl-or $expand

Union of Cellulitis subtree and Liver-structure subtree.

snomed-expand-ecl-and $expand

Intersection: Cellulitis subtree AND Disease subtree; should equal << 128045006.

snomed-expand-ecl-minus $expand

Exclusion: Disease subtree minus Cellulitis subtree.

snomed-expand-ecl-minus-empty $expand

Degenerate exclusion: set minus itself, expects empty.

snomed-expand-ecl-wildcard-minus $expand

All active concepts minus the Liver-structure subtree.

snomed-expand-ecl-grouped-or $expand

Grouped OR: (<< A OR << B) AND << C — OR subexpression parenthesised; union of cellulitis and liver-structure subtrees intersected with disease; yields 1 result.

snomed-expand-ecl-grouped-and $expand

Grouped AND: << A OR (<< B AND << C) — AND subexpression parenthesised; liver-structure unioned with intersection of cellulitis and disease; yields 311 results.

snomed-expand-ecl-ambiguous-precedence $expand

Invalid ECL: mixing AND/OR without explicit grouping is forbidden by ECL spec (section 6.4) — must return an error.

snomed-expand-ecl-member-filter-misplaced $expand

Invalid ECL: a member filter {{ M ... }} may only follow a memberOf (^) constraint. ( ^ A OR ^ B ... ) {{ M effectiveTime >= "20250101" }} attaches it to a bracketed disjunction instead — must return a syntax error.

snomed-expand-ecl-member-filter-date-in $expand

Member filter: ^ 900000000000526001 {{ M effectiveTime >= "20240101" }} - both REPLACED BY members in the test edition (member rows dated 20240601 and 20250909) are selected; yields 2 results.

snomed-expand-ecl-member-filter-date-out $expand

Member filter: ^ 900000000000526001 {{ M effectiveTime >= "20250101" }} - the corrected (^ outside the brackets) form of the misplaced test, trimmed to the one association reference set in the test edition; only the member row dated 20250909 is selected (1 result).

snomed-expand-ecl-operator-on-set $expand

Hierarchy operator on a bracketed set: <! (A OR B) is the union of <! A and <! B (5 results). A server that drops the operator would return A and B themselves.

snomed-expand-ecl-operator-on-set-ancestors $expand

Ancestor operator on a bracketed set: > (A OR B) is the union of > A and > B (24 results).

snomed-expand-ecl-operator-on-memberOf $expand

Hierarchy operator on ^: << ^ refset is the members and their descendants; both REPLACED BY members are inactive and have no descendants (2 results).

snomed-expand-ecl-top-of-set $expand

Top of set: !!> (<< A OR << B) yields A and B (2 results).

snomed-expand-ecl-top-of-set-children $expand

Top of set: !!> (< A) is the direct children of A (4 results).

snomed-expand-ecl-bottom-of-set $expand

Bottom of set: !!< (<< A) is the leaves below A (1 result).

snomed-expand-ecl-refinement-or $expand

Refinement OR: attributes joined by OR (22 results, the union of 3 and 19 disjoint results).

snomed-expand-ecl-refinement-and $expand

Refinement AND: the same as the comma form; nothing has both attributes (0 results).

snomed-expand-ecl-refinement-group-or $expand

Refinement OR between attribute groups (22 results).

snomed-expand-ecl-refinement-or-in-group $expand

Refinement OR inside an attribute group (22 results).

snomed-expand-ecl-attribute-name-expression $expand

Attribute name as an expression: << 762705008 = << Lung (3 results, the same as 363698007 = << Lung).

snomed-expand-ecl-attribute-name-set $expand

Attribute name as a bracketed set: (A OR B) = value (3 results).

snomed-expand-ecl-attribute-name-wildcard $expand

Attribute name wildcard: * = << Lung (3 results).

snomed-expand-ecl-dotted-expression-attribute $expand

Dotted expression with an expression attribute name (4 results).

snomed-expand-ecl-comment $expand

Comments (/* ... */) are whitespace (3 results).

snomed-expand-ecl-concept-filter-primitive $expand

Concept filter definitionStatus = primitive on the children of Disease.

snomed-expand-ecl-concept-filter-defined $expand

Concept filter definitionStatus = defined on the children of Disease; with the primitive twin partitions the 25 children.

snomed-expand-ecl-concept-filter-effectiveTime $expand

Concept filter effectiveTime >= "20200101" (22 of 310 results).

snomed-expand-ecl-concept-filter-inactive $expand

Concept filter active = false: the inactive concepts of the test edition (7 results).

snomed-expand-ecl-description-filter-term $expand

Description filter term = "lobe liv": each search word must start a word of the same active description (27 results).

snomed-expand-ecl-description-filter-term-no-d $expand

Description filter without the D: {{ term = "lobe liv" }} - ECL 2.2 makes the D optional, so this is the same filter as snomed-expand-ecl-description-filter-term, with the same 27 results

snomed-expand-ecl-description-filter-term-set $expand

Description filter with a term set - any of the terms may match (26 results).

snomed-expand-ecl-description-filter-term-wild $expand

Description filter with a wild: search term matched against the whole description (37 results).

snomed-expand-ecl-description-filter-typeId $expand

Description filter typeId = Synonym with a term that only the FSN carries: the filters apply to one description, so nothing matches (0 results).

snomed-expand-ecl-description-filter-typeId-fsn $expand

Description filter typeId = FSN with the semantic tag as the term: every concept matches (310 results).

snomed-expand-ecl-description-filter-language $expand

Description filter language = fr on an English-only edition (0 results).

snomed-expand-ecl-description-filter-language-en $expand

Description filter language = en: every child of Liver structure has one (4 results).

snomed-expand-ecl-description-filter-active $expand

Description filter active = false: concepts with an inactive description matching the term (3 results, all inactive concepts).

snomed-expand-ecl-description-filter-active-default $expand

Description filter with no active filter considers active descriptions only, on active and inactive concepts alike (4 results).

snomed-expand-ecl-description-filter-two-blocks $expand

Two {{ D }} blocks AND at the concept level (27 results).

snomed-expand-ecl-memberOf-descriptions $expand

^ on a language reference set: its members are descriptions, not concepts. The server reports that the expression cannot be evaluated (UNSUPPORTED_ECL), rather than returning an empty expansion.

snomed-expand-ecl-memberOf-field-selection $expand

Reference set field selection ^ [referencedComponentId] on a language reference set: syntactically valid ECL 2.x whose result would be descriptions. Expected to be reported as not supported (UNSUPPORTED_ECL), not as a syntax error. Whether field selection on concept-valued fields (^ [targetComponentId] ...) is in scope is for the committee.

snomed-expand-ecl-memberOf-any $expand

Snow Owl memberOfAny: ^ * is every concept that is a member of any reference set; description-member reference sets contribute nothing.

snomed-expand-ecl-memberOf-nested $expand

Snow Owl memberOfNested: ^ (< 900000000000455006) is the union of the members of every reference set below the root.

snomed-expand-ecl-operator-on-memberOf-descendants $expand

Snow Owl descendantsOfAllMembersOfReferenceSet: < ^ refset is the union of < each member.

snomed-expand-ecl-descendant-of-any $expand

Snow Owl descendantOfAny: < * is every concept with a parent. count=0, so only the total is compared.

snomed-expand-ecl-child-of-any $expand

Snow Owl childOfAny: <! * is the same set as < *. count=0, so only the total is compared.

snomed-expand-ecl-descendant-or-self-of-any $expand

Snow Owl descendantOrSelfAny: << * is *. count=0, so only the total is compared.

snomed-expand-ecl-child-or-self-of-any $expand

Snow Owl childOrSelfOfAny: <<! * is *. count=0, so only the total is compared.

snomed-expand-ecl-ancestor-or-self-of-any $expand

Snow Owl ancestorOrSelfOfAny: >> * is *. count=0, so only the total is compared.

snomed-expand-ecl-top-of-any $expand

Snow Owl topOfAny: !!> * is the roots - 138875005 plus the subset's orphaned module, metadata and inactive concepts.

snomed-expand-ecl-bottom-of-any $expand

Snow Owl bottomOfAnyTooCostly: !!< * is every leaf. count=0, so only the total is compared; a server may answer or may decline as too costly, which this test does not allow for.

snomed-expand-ecl-self-and-self $expand

Snow Owl selfAndSelf: A AND A is {A}.

snomed-expand-ecl-comma-conjunction $expand

Snow Owl selfAndOtherWithCommaAsOperator: "A , B" is A AND B, and is empty for two different concepts.

snomed-expand-ecl-and-chain $expand

Snow Owl multipleAndOperatorsWithoutBrackets: an AND chain of three without brackets.

snomed-expand-ecl-or-chain $expand

Snow Owl multipleOrOperatorsWithoutBrackets: an OR chain of three without brackets.

snomed-expand-ecl-ambiguous-precedence-and-or $expand

Snow Owl binaryOperatorAmbiguityAndOr: AND then OR without brackets is a syntax error (the existing test covers OR then AND).

snomed-expand-ecl-ambiguous-or-in-refinement $expand

Snow Owl ambiguousOrOperatorInRefinement: an OR after a refinement binds inside it, leaving an attribute without a comparison - a syntax error.

snomed-expand-ecl-or-with-refined-operand $expand

Snow Owl ambiguousOrOperatorInConstraint: A OR (< B : attr = value) - the refinement binds to its own operand.

snomed-expand-ecl-refinement-attribute-and-value-sets $expand

Snow Owl refinementAttributeSubExpression: (A OR B) = (X OR Y) in a refinement.

snomed-expand-ecl-refinement-not-equals $expand

Snow Owl refinementAttributeNotEquals: A != X matches concepts with at least one A whose value is not X.

snomed-expand-ecl-refinement-not-equals-any $expand

Snow Owl refinementAnyAttributeNotEquals: * : A != X.

snomed-expand-ecl-refinement-reverse $expand

Snow Owl refinementReversedAttributeEquals: R A = X yields the values of A on X.

snomed-expand-ecl-refinement-reverse-any-attribute $expand

Snow Owl refinementAnyAttributeName: R * = X yields every substance that is an attribute value of X.

snomed-expand-ecl-refinement-reverse-any-value $expand

Snow Owl refinementAnyAttributeValue: R A = * yields every substance that is the value of A somewhere.

snomed-expand-ecl-refinement-reverse-cardinality $expand

Snow Owl refinementReversedCardinalityZeroToUnbounded: [0..*] R A = X is satisfied by every concept in the focus set.

snomed-expand-ecl-refinement-cardinality-zero-to-many $expand

Snow Owl refinementCardinalityZeroToUnbounded: [0..*] A = X is every concept in the focus set.

snomed-expand-ecl-refinement-cardinality-at-least-one $expand

Snow Owl refinementCardinalityAtLeastOne: [1..*] A = X equals A = X.

snomed-expand-ecl-refinement-cardinality-zero $expand

Snow Owl refinementCardinalityZeroToZeroEquals: [0..0] A = X is the concepts with no such attribute.

snomed-expand-ecl-refinement-cardinality-zero-not-equals $expand

Snow Owl refinementCardinalityZeroToZeroNotEquals: [0..0] A != X is the concepts whose every A is in X (including those with no A).

snomed-expand-ecl-refinement-cardinality-zero-not-equals-single $expand

Snow Owl refinementCardinalityZeroToZeroNotEqualsToSingleValue: [0..0] A != x excludes exactly the concepts with an A whose value is not x.

snomed-expand-ecl-refinement-cardinality-zero-to-one $expand

Snow Owl refinementCardinalityZeroToOne: [0..1] A = X.

snomed-expand-ecl-refinement-cardinality-one-to-two $expand

Snow Owl refinementCardinalityOneOrTwo: [1..2] A = X.

snomed-expand-ecl-refinement-nested-and-or $expand

Snow Owl refinementWithConjunctionAndDisjunction: A = x OR (B = y AND C = y), where the bracketed AND matches nothing.

snomed-expand-ecl-refinement-ambiguous-and-or $expand

Snow Owl refinementAmbiguityAndOr: AND then OR between refinements without brackets is a syntax error.

snomed-expand-ecl-refinement-ambiguous-or-and $expand

Snow Owl refinementAmbiguityOrAnd: OR then AND between refinements without brackets is a syntax error.

snomed-expand-ecl-dotted-single-concept $expand

Snow Owl dotted: X . A on a single concept yields the values of A on X.

snomed-expand-ecl-dotted-complex-left-side $expand

Snow Owl dottedWithComplexLeftSide: (A MINUS B) . attr.

snomed-expand-ecl-group-cardinality-two $expand

Snow Owl refinementGroupCardinalityTwoToTwo: [2..2] { ... }.

snomed-expand-ecl-group-cardinality-zero-to-many $expand

Snow Owl refinementGroupCardinalityZeroToUnbounded: [0..*] { ... } is every concept in the focus set.

snomed-expand-ecl-group-cardinality-zero $expand

Snow Owl refinementGroupCardinalityZeroToZero / groupCardinalityZeroToZeroWithDefaultAttributeCardinality: [0..0] { ... }.

snomed-expand-ecl-group-cardinality-zero-to-one $expand

Snow Owl refinementGroupCardinalityZeroToOne / groupCardinalityZeroToOneWithDefaultAttributeCardinality: [0..1] { ... }.

snomed-expand-ecl-group-cardinality-with-conjunction $expand

Snow Owl refinementWithGroupConjunction: [1..1] { A = X, B = Y }.

snomed-expand-ecl-group-cardinality-with-disjunction $expand

Snow Owl refinementWithGroupDisjunction: [1..1] { A = x OR B = x }.

snomed-expand-ecl-group-nested-and-or $expand

Snow Owl refinementGroupNestedConjunctionDisjunction: [1..1] { (A = x AND B = x) OR C = x }.

snomed-expand-ecl-group-attribute-cardinality-zero $expand

Snow Owl defaultGroupCardinalityWithZeroToZeroAttributeCardinality: { [0..0] A = X }. Snow Owl says empty; this test expects the groups-without-the-attribute reading. Needs confirmation.

snomed-expand-ecl-group-attribute-cardinality-zero-not-equals $expand

Snow Owl defaultGroupCardinalityWithZeroToZeroAttributeCardinalityNotEquals: { [0..0] A != x }.

snomed-expand-ecl-group-attribute-cardinality-zero-to-one $expand

Snow Owl defaultGroupCardinalityWithZeroToOneAttributeCardinality: { [0..1] A = X }.

snomed-expand-ecl-group-cardinality-zero-to-one-not-equals $expand

Snow Owl groupCardinalityZeroToOneWithDefaultAttributeCardinalityNotEquals: [0..1] { A != X }.

snomed-expand-ecl-group-and-attribute-cardinality-zero-zero $expand

Snow Owl groupCardinalityZeroToZeroWithZeroToZeroAttributeCardinality: [0..0] { [0..0] A = X }. Snow Owl says empty. Needs confirmation.

snomed-expand-ecl-group-and-attribute-cardinality-zero-one-zero-zero $expand

Snow Owl groupCardinalityZeroToOneWithZeroToZeroAttributeCardinality: [0..1] { [0..0] A = X }. Snow Owl says empty. Needs confirmation.

snomed-expand-ecl-group-and-attribute-cardinality-zero-zero-zero-one $expand

Snow Owl groupCardinalityZeroToZeroWithZeroToOneAttributeCardinality: [0..0] { [0..1] A = X } matches nothing.

snomed-expand-ecl-group-and-attribute-cardinality-zero-one-zero-one $expand

Snow Owl groupCardinalityZeroToOneWithZeroToOneAttributeCardinality: [0..1] { [0..1] A = X }.

snomed-expand-ecl-group-mixed-attribute-cardinalities $expand

Snow Owl refinementWithZeroToOneCardinalityInAttributeConjuction: { [0..1] A = X, [1..1] B = Y }.

snomed-expand-ecl-concrete-integer-equals $expand

Snow Owl refinementIntegerEquals: A = #n on an integer-valued attribute.

snomed-expand-ecl-concrete-integer-equals-large $expand

Snow Owl refinementIntegerEquals: A = #n selecting one product.

snomed-expand-ecl-concrete-integer-not-equals $expand

Snow Owl refinementIntegerNotEquals: A != #n matches concepts with a value of A other than n (0 results here).

snomed-expand-ecl-concrete-integer-less-than $expand

Snow Owl refinementIntegerLessThan: A < #n.

snomed-expand-ecl-concrete-integer-less-than-or-equals $expand

Snow Owl refinementIntegerLessThanOrEquals: A <= #n.

snomed-expand-ecl-concrete-integer-greater-than $expand

Snow Owl refinementIntegerGreaterThan: A > #n.

snomed-expand-ecl-concrete-integer-greater-than-or-equals $expand

Snow Owl refinementIntegerGreaterThanEquals: A >= #n.

snomed-expand-ecl-concrete-integer-negative $expand

Snow Owl refinementIntegerEqualsNegative: #-n parses; 0 results in the test edition.

snomed-expand-ecl-concept-filter-active-not-equals $expand

Snow Owl concept_active_notequals: {{ C active != false }}.

snomed-expand-ecl-description-filter-term-match-and-wild $expand

Snow Owl termDisjunction: {{ D term = (match:"..." wild:"...") }}.

snomed-expand-ecl-description-filter-wild-case-insensitive $expand

Snow Owl termWildCaseInsensitive: wild: matching ignores case.

snomed-expand-ecl-description-filter-wild-any $expand

Snow Owl termWildAnyCharacterShouldNotCreateQueryClause: wild:"**" matches everything.

snomed-expand-ecl-filters-across-and $expand

Snow Owl multiDomainQueryAnd: filters on each side of AND.

snomed-expand-ecl-filters-across-or $expand

Snow Owl multiDomainQueryOr: filters on each side of OR.

snomed-expand-ecl-filters-across-minus $expand

Snow Owl multiDomainQueryExclusion: filters on each side of MINUS.

snomed-expand-ecl-history-default $expand

Snow Owl profile_default: {{ + HISTORY }} adds the inactive concepts associated with the result (here, through REPLACED BY).

snomed-expand-ecl-history-max $expand

Snow Owl profile_max: {{ + HISTORY-MAX }}.

snomed-expand-ecl-history-mod $expand

Snow Owl profile_mod: {{ + HISTORY-MOD }} includes REPLACED BY.

snomed-expand-ecl-history-min $expand

Snow Owl profile_min: {{ + HISTORY-MIN }} is SAME AS only; nothing is added in the test edition.

snomed-expand-ecl-history-explicit-refset $expand

Snow Owl profile_explicit_refsets: {{ + HISTORY (refset) }} with an explicit reference set.

snomed-expand-ecl-history-all-refsets $expand

Snow Owl profile_all_association_refsets: {{ + HISTORY (*) }}.

snomed-expand-ecl-alt-identifier $expand

Alternate identifier (ECL 2.1): LOINC#code resolves to the concept carrying that LOINC code in the LOINC Extension.

snomed-expand-ecl-alt-identifier-quoted-operator $expand

Alternate identifier in quotes with a hierarchy operator: >> "LOINC#code".

snomed-expand-ecl-alt-identifier-unknown $expand

An alternate identifier that no concept carries is an invalid expression, like an unknown concept.

snomed-expand-ecl-term-match $expand

Concept reference with matching term; should be accepted.

snomed-expand-ecl-term-mismatch $expand

Concept reference with incorrect term; should error with a term-mismatch message.

snomed-expand-ecl-term-with-operator $expand

Hierarchy operator plus concept plus term; should expand to same set as << 10200004.

snomed-expand-ecl-unknown-concept $expand

Unknown (non-existent) concept ID; expects an unknown-concept error.

snomed-expand-ecl-invalid-sctid $expand

Non-numeric focus concept; expects a lexer/parser error.

snomed-expand-ecl-missing-focus $expand

Operator with nothing after it; expects a parser error.

snomed-expand-ecl-trailing-tokens $expand

Extra tokens after a complete expression; expects a parser error.

snomed-expand-ecl-nested-parens $expand

Deeply nested parentheses; should expand to the same set as << 10200004.

snomed-expand-ecl-refinement-simple $expand

Refinement: Disease with finding-site in the Liver subtree. Currently unsupported; expect a clear error.

snomed-expand-ecl-refinement-morphology $expand

Refinement: Disease with associated-morphology = Closed fracture. Currently unsupported.

snomed-expand-ecl-refinement-wildcard $expand

Refinement with wildcard value. Currently unsupported.

snomed-expand-ecl-refinement-group $expand

Refinement with an attribute group. Currently unsupported.

snomed-expand-ecl-refinement-cardinality $expand

Ungrouped [1..1] cardinality: exactly 1 Finding site in liver across all role groups — excludes concepts with 2+ groups each containing a liver Finding site (573).

snomed-expand-ecl-refinement-cardinality-grouped $expand

Grouped [1..1] cardinality: exactly 1 role group containing exactly 1 Finding site in liver — same result as ungrouped for typical SNOMED models (573).

snomed-expand-ecl-refinement-cardinality-rolegroup $expand

Role group cardinality without outer count: at least one role group containing exactly 1 Finding site in liver — more permissive, includes concepts with multiple groups each having 1 liver Finding site (661).

snomed-expand-ecl-dotted $expand

Dotted expression: finding-site values across Disease descendants. Currently unsupported.

snomed-expand-ecl-refinement-inactive-rel $expand

Inactive relationships are ignored: a refinement (363698007 = Kidney structure) does not match 50325005, whose only Kidney finding site row is inactive

snomed-expand-ecl-descendants-inactive-isa $expand

Inactive relationships are ignored: << Hepatorenal syndrome does not include 50325005, whose is-a row to it is inactive

snomed-expand-ecl-description-filter-wild-all-language $expand

Description filter over the whole edition with a language: * {{ D term = wild:"hematoma", language = en }} - the same concepts as the display regex test snomed-expand-display-regex

snomed-expand-ecl-description-filter-wild-nl $expand

Description filter in another language: * {{ D term = wild:"hematoom", language = nl }} - the same concepts as snomed-expand-display-regex-nl, with the default (English) displays

snomed-expand-ecl-concrete-decimal-literal $expand

A decimal literal against an integer-valued attribute: concentration strength numerator > #599.5 (1 result)

snomed-expand-ecl-concrete-decimal $expand

Decimal concrete values (test edition extension): test potency >= #0.75 matches both #0.75 and #2.5 (2 results)

snomed-expand-ecl-concrete-decimal-equals $expand

Decimal concrete values compare by value: #2.50 equals #2.5 (1 result)

snomed-expand-ecl-concrete-grouped $expand

Two concrete values in the same relationship group: presentation strength 4000 per 1 (1 result)

snomed-expand-ecl-concrete-type-mismatch $expand

A string value never matches a numeric concrete value, even one that reads the same: nothing has presentation strength numerator "4000" (0 results)

snomed-expand-ecl-concrete-string $expand

String concrete values (test edition extension): the nickname is exactly "Barium milkshake" (1 result)

snomed-expand-ecl-concrete-string-not-equals $expand

String concrete values: != matches the concepts that have the attribute with another value (a concept without the attribute does not match) (1 result)

snomed-expand-ecl-concrete-string-wild $expand

String concrete values with a wild search term: a nickname ending in capsule (1 result)

snomed-expand-ecl-concrete-boolean-true $expand

Boolean concrete values (test edition extension): fish-derived products (2 results)

snomed-expand-ecl-concrete-boolean-false $expand

Boolean concrete values: products that are not fish-derived (1 result)

snomed-validate-ecl-concrete-code-in $validate-code

validate-code against a concrete value refinement: presentation strength numerator = #4000: a code that IS in the set

snomed-validate-ecl-concrete-code-out $validate-code

validate-code against a concrete value refinement: presentation strength numerator = #4000: a code that is NOT in the set

snomed-expand-ecl-memberOf-simple-map $expand

Map reference sets have members: a simple map (mapTarget) with two members

snomed-expand-ecl-memberOf-extended-map $expand

Map reference sets have members: an extended map with three active rows for two concepts (one concept is mapped in two map groups) and an inactive row for a third; each member concept appears once, and the inactive row does not count

snomed-expand-ecl-member-filter-map-target $expand

A member filter on a map reference set field: the extended map rows whose mapTarget is Y92.9

batch general

Test Batch Validation

batch-validate $batch-validate

Simple use of the batch validate operation

batch-validate-bad $batch-validate

Simple use of the batch validate operation

cs-batch-validate $cs-batch-validate

Simple use of the batch validate operation against a code system (CodeSystem/$batch-validate-code): good, inactive and unknown codes, with the code system given once at the top level

cs-batch-validate-bad $cs-batch-validate

Batch validate against a code system where an entry overrides a top-level parameter (lenient-display-validation), and one entry cannot be validated at all

cs-batch-validate-codings $cs-batch-validate

Batch validate against code systems with no top-level url: each entry is a Coding that names its own system, including one the server does not know

omop omop

Tests for OMOP implementations. Note that some servers only do OMOP (and some don't). The tests are based on a stable subset of OMOP maintained by Davera Gabriel

omop-basic-validation-code-good $cs-validate-code

Just validate a randomly chosen real OMOP code provided as system and code

omop-basic-validation-coding-good $cs-validate-code

Just validate a randomly chosen real OMOP code provided as coding

omop-basic-validation-codeableconcept-good $cs-validate-code

Just validate a randomly chosen real OMOP code provided as codeableConcept

omop-basic-validation-code-bad $cs-validate-code

Just validate a randomly chosen fake OMOP code that is not valid provided as system and code

omop-basic-validation-coding-bad $cs-validate-code

Just validate a randomly chosen fake OMOP code that is not valid provided as coding

omop-basic-validation-codeableconcept-bad $cs-validate-code

Just validate a randomly chosen fake OMOP code that is not valid provided as CodeableConcept

omop-basic-validation-code-bad-display $cs-validate-code

Just validate a randomly chosen real OMOP code with a wrong display provided as system, code and display

omop-basic-validation-coding-bad-display $cs-validate-code

Just validate a randomly chosen real OMOP code with a wrong display provided as coding

omop-basic-validation-codeableconcept-bad-display $cs-validate-code

Just validate a randomly chosen real OMOP code with a wrong display provided as CodeableConcept

omop-basic-validation-code-bad-version $cs-validate-code

Just validate a randomly chosen real OMOP code with a wrong display provided as system, code and display

omop-basic-validation-coding-bad-version $cs-validate-code

Just validate a randomly chosen real OMOP code with a wrong display provided as coding

omop-basic-validation-codeableconcept-bad-version $cs-validate-code

Just validate a randomly chosen real OMOP code with a wrong display provided as CodeableConcept

omop-basic-validation-code-good-vs $validate-code

Just validate a randomly chosen real OMOP code provided as system and code and require that it's in a particular domain by value set (it is!)

omop-basic-validation-coding-good-vs $validate-code

Just validate a randomly chosen real OMOP code provided as a coding and require that it's in a particular domain by value set (it is!)

omop-basic-validation-codeableconcept-good-vs $validate-code

Just validate a randomly chosen real OMOP code provided as a CodeableConcept and require that it's in a particular domain by value set (it is!)

omop-basic-validation-code-bad-vs $validate-code

Just validate a randomly chosen real OMOP code provided as system and code and require that it's in a particular domain by value set (it is not!)

omop-basic-validation-coding-bad-vs $validate-code

Just validate a randomly chosen real OMOP code provided as a coding and require that it's in a particular domain by value set (it is not!)

omop-basic-validation-codeableconcept-bad-vs $validate-code

Just validate a randomly chosen real OMOP code provided as a CodeableConcept and require that it's in a particular domain by value set (it is not!)

omop-lookup-code $lookup

Lookup a standard OMOP code

omop-lookup-code2 $lookup

lookup a non-standard OMOP Code

omop-lookup-code3 $lookup

lookup a non-standard OMOP Code

omop-basic-validation-code-good-vs-url $validate-code

Same as omop-basic-validation-code-good-vs but passing a value set in

omop-basic-validation-code-bad-vs-url $validate-code

Same as omop-basic-validation-code-bad-vs but passing a value set in

omop-expand-explicit $expand

Expand an OMOP value set

omop-expand-property $expand

Properties asked for with the property parameter are returned on each code in the expansion (and declared in expansion.property)

translate-loinc-implicit $translate

translating sucessfully from OMOP to LOINC, leaving it to the server to choose a concept map if it can find one. Note that not all servers are willing to let the client trust it like this, so this test is optional

translate-loinc-implicit-bad $translate

translating unsucessfully from OMOP to LOINC, leaving it to the server to choose a concept map if it can find one, Also this test - and the last one - assume that the server has no other source of OMOP -> LOINC mappings available

UCUM tx.fhir.org

UCUM Test Cases

lookup $lookup

Tests the $lookup operation

lookup-with-annotation $lookup

Tests the $lookup operation with annotation

expand-ucum-all-4 $expand version: 4.0

Tests the $expand operation for all codes (this is a special case). The special value set changed between R4 and R5

expand-ucum-all-5 $expand version: 5.0

Tests the $expand operation for all codes (this is a special case). The special value set changed between R4 and R5

expand-ucum-canonical $expand

Tests the $expand operation for all codes (this is a special case)

expand-ucum-property $expand

The canonical property, asked for with the property parameter, is returned on each code in the expansion (and declared in expansion.property)

validate-ucum-canonical-good $validate-code

Tests the $validate-code operation for a valid UCUM code

validate-ucum-canonical-bad $validate-code

Tests the $validate-code operation for an valid UCUM code not in the canonicl value set

validate-all-canonical-good $validate-code

Tests the $validate-code operation for a valid UCUM code

validate-ucum-all-bad $validate-code

Tests the $validate-code operation for an invalid UCUM code

ucum-subsumes-equivalent $subsumes

A unit is equivalent to itself

ucum-subsumes-canonical $subsumes

The same unit written two different ways

ucum-subsumes-unrelated $subsumes

Two unrelated units

ucum-subsumes-scaled $subsumes

A unit and a scaled version of it - UCUM has no hierarchy

ucum-subsumes-invalid-code $subsumes

codeA is not a valid UCUM unit

ucum-subsumes-annotation $subsumes

A unit with an annotation, and the same unit without

ucum-subsumes-derived $subsumes

A named derived unit and the expression it is defined as

ucum-subsumes-offset $subsumes

Two units of the same property whose conversion has an offset

ucum-subsumes-same-canonical $subsumes

Two units with the same canonical unit but different magnitudes

ucum-subsumes-both-scaled $subsumes

The same canonical unit again, with neither magnitude being 1

ucum-subsumes-dimensionless $subsumes

Two dimensionless units, told apart only by magnitude

mimetypes mimetypes

Tests for the mime types code system (BCP 13). Type and subtype have no hierarchy, but parameters narrow a media type, and the base filter selects by type or type/subtype

mimetype-subsumes-equivalent $subsumes

A media type is equivalent to itself

mimetype-subsumes-unrelated $subsumes

Two unrelated media types

mimetype-subsumes-suffix $subsumes

A media type and one with a structured suffix of it

mimetype-subsumes-parameter $subsumes

A media type and the same type carrying a parameter

mimetype-subsumes-parameter-reverse $subsumes

the mirror of mimetype-subsumes-parameter

mimetype-subsumes-parameter-siblings $subsumes

The same parameter with two different values

mimetype-subsumes-parameter-added $subsumes

A parameter set and a superset of it

mimetype-subsumes-parameter-disjoint $subsumes

Two parameter sets, neither containing the other

mimetype-subsumes-default-explicit $subsumes

a parameter written out at its default value: RFC 6657 section 4 keeps US-ASCII as the default charset for text/plain, so the bare form already carries it and the two codes are the same media type

mimetype-subsumes-default-contradicted $subsumes

a parameter away from its default: because bare text/plain means charset=us-ascii, a different charset contradicts it rather than narrowing it. This is where the rule that a parameter narrows does not hold

mimetype-subsumes-default-format $subsumes

the same for format, which RFC 3676 section 4 defaults to Fixed, so text/plain and text/plain; format=flowed are different media types

mimetype-subsumes-charset-unknown-default $subsumes

RFC 6657 section 3 leaves a text/* registration that does not say how the charset is determined defaulting to US-ASCII, so for such a type a server cannot tell whether the absence of a charset means any charset or means US-ASCII, and the two give opposite answers

mimetype-subsumes-case $subsumes

The same media type differing only in case and quoting

mimetype-subsumes-unknown-parameter $subsumes

a parameter the server does not know: whether it narrows the media type depends on its definition, so the relationship cannot be determined

mimetype-subsumes-unknown-parameter-value $subsumes

two values of an unknown parameter: nothing says whether they exclude one another or one includes the other

mimetype-subsumes-unknown-parameter-shared $subsumes

an unknown parameter carried identically by both codes cannot affect the answer, so it must not stop the server deciding

mimetype-subsumes-invalid-code $subsumes

codeA is not a well formed media type

mimetype-filter-base-type-in $validate-code

A code whose type matches a base filter of 'text'

mimetype-filter-base-type-params $validate-code

Parameters do not stop a code matching the base filter

mimetype-filter-base-type-other-subtype $validate-code

Any subtype of the type matches a type-only base filter

mimetype-filter-base-type-out $validate-code

A code of a different type does not match

mimetype-filter-base-subtype-in $validate-code

A code matching a base filter of 'text/plain'

mimetype-filter-base-subtype-params $validate-code

Parameters do not stop a code matching a type/subtype base filter

mimetype-filter-base-subtype-out $validate-code

A different subtype does not match a type/subtype base filter

mimetype-filter-registered-in $validate-code

A media type that is in the IANA registry

mimetype-filter-registered-params $validate-code

Parameters do not stop a registered type matching

mimetype-filter-registered-out $validate-code

A media type that is not in the IANA registry

mimetype-filter-unregistered-in $validate-code

registered=false selects a type that is not in the registry

mimetype-filter-unregistered-out $validate-code

registered=false excludes a registered type

mimetype-filter-registered-params-out $validate-code

A parameter does not make an unregistered type match registered=true

mimetype-filter-unregistered-params-in $validate-code

An unregistered type with a parameter still matches registered=false

mimetype-filter-unregistered-params-out $validate-code

A parameter does not make a registered type match registered=false

mimetype-expand-enumerated $expand

An enumerated list of media types expands

mimetype-expand-all $expand

The whole code system cannot be expanded

mimetype-expand-base $expand

A base filter cannot be expanded either

mimetype-expand-unregistered $expand

registered=false cannot be expanded - it is unbounded

mimetype-expand-registered-narrow $expand

registered=true can be expanded, narrowed by a base filter, and the expansion is marked unclosed

mimetype-expand-registered-too-costly $expand

Expanding every registered media type at once is too costly

mimetype-expand-registered-paged $expand

A page of the registered media types, with the page size asserted rather than its contents

compare tx.fhir.org

Tests for candidate new 'related' operation

related-all $compare

Checks that an all value is the same as itself

related-active $compare

Checks that an all value is the same as itself, in the presence of the active flag = true

related-inactive $compare

Checks that an all value is the same as itself, in the presence of the active flag = false

related-enumerated $compare

Checks that an all value is the same as itself, in the presence of an enumerated list

related-is-a $compare

Checks that an all value is the same as itself, in the presence of an is-a filter

related-regex-1 $compare

Checks that an all value is the same as itself, in the presence of an regex filter

related-regex-2 $compare

Checks that an all value is the same as itself, in the presence of a property regex filter

related-lists $compare

Checks that two enumerated value sets are the same (concept order is different)

related-lists-more $compare

Checks that two enumerated value sets are related such that the other contains this

related-lists-less $compare

Checks that two enumerated value sets are related such that this contains the other

related-lists-over $compare

Checks that two enumerated value sets are overlapping

related-lists-disj $compare

Checks that two enumerated value sets are the disjoint

related-systems $compare

Checks that two valuesets that import the same entire code systems are identical

related-systems $compare

Checks that two valuesets that import the same entire code systems are identical

related-systems-less $compare

Checks that two valuesets that import the same entire code systems are identical

related-systems-more $compare

Checks that two valuesets that import the same entire code systems are identical

related-system-disj $compare

Checks that two valuesets that import the same entire code systems are identical

related-system-over $compare

Checks that two valuesets that import the same entire code systems are identical

related-filters-1 $compare

Checks that two valuesets that haev the same filters in different orders (as filters)

related-filters-2 $compare

Checks that two valuesets that haev the same filters in different orders (as includes)

related-filters-3 $compare

Checks that two valuesets that haev the same filters in different orders (as includes from the same system)

related-mixed-1 $compare

Checks that two valuesets that have the same content with incompatible definitions are considered the same

related-mixed-1-less $compare

Checks that two valuesets that have the same content with incompatible definitions are considered the same

related-mixed-1-more $compare

Checks that two valuesets that have the same content with incompatible definitions are considered the same

related-mixed-1-disj $compare

Checks that two valuesets that have the same content with incompatible definitions are considered the same

related-mixed-1-over $compare

Checks that two valuesets that have the same content with incompatible definitions are considered the same

related-filters-less $compare

Checks that two valuesets that have the same content with incompatible definitions are considered the same

related-filters-more $compare

Checks that two valuesets that have the same content with incompatible definitions are considered the same

bugs tx.fhir.org

A series of tests that deal with discovered bugs in FHIRsmith. These tests are specific to FHIRsmith - internal QA

country-codes $expand
cpt $expand
cpt-1000 $expand

Check that the 1000 code agreement made with AMA is enforced correctly

cpt-0 $expand
cpt-100 $expand
sct-ver-ex $expand
undefined $validate-code
no-system $cs-validate-code
sct-parse $cs-validate-code
sct-parse-pc $cs-validate-code
lang-case $cs-validate-code
lang-case2 $cs-validate-code
provenance $cs-validate-code
country-code $cs-validate-code
sct-isa $validate-code
sct-ver $cs-validate-code
sct-msg-4 $validate-code version: 4.0
sct-msg-5 $validate-code version: 5.0
sct-display-1 $cs-validate-code
sct-display-2 $cs-validate-code
ndc $cs-validate-code
x12-bad $cs-validate-code
3166-a $cs-validate-code

Check user assigned codes are valid

3166-b $cs-validate-code

Check user assigned codes can get display from a supplement

3166-c $cs-validate-code

But base names are still valid

3166-d $cs-validate-code

Check that wrong displays on user assigned codes are just a hint

exclude-limit $expand

A value set with an exclude is held to the response limit

import-limit $expand

Codes from an imported value set count against the response limit

permutations general

A set of permutations generated by Claude with the goal of increasing test coverage.

bad-cc1-all-request $validate-code
bad-cc1-enumerated-request $validate-code
bad-cc1-exclude-filter-request $validate-code
bad-cc1-exclude-import-request $validate-code
bad-cc1-exclude-list-request $validate-code
bad-cc1-import-request $validate-code
bad-cc1-isa-request $validate-code
bad-cc2-all-request $validate-code
bad-cc2-enumerated-request $validate-code
bad-cc2-exclude-filter-request $validate-code
bad-cc2-exclude-import-request $validate-code
bad-cc2-exclude-list-request $validate-code
bad-cc2-import-request $validate-code
bad-cc2-isa-request $validate-code
bad-coding-all-request $validate-code
bad-coding-enumerated-request $validate-code
bad-coding-exclude-filter-request $validate-code
bad-coding-exclude-import-request $validate-code
bad-coding-exclude-list-request $validate-code
bad-coding-import-request $validate-code
bad-coding-isa-request $validate-code
bad-scd-all-request $validate-code
bad-scd-enumerated-request $validate-code
bad-scd-exclude-filter-request $validate-code
bad-scd-exclude-import-request $validate-code
bad-scd-exclude-list-request $validate-code
bad-scd-import-request $validate-code
bad-scd-isa-request $validate-code
good-cc1-all-request $validate-code
good-cc1-enumerated-request $validate-code
good-cc1-exclude-filter-request $validate-code
good-cc1-exclude-import-request $validate-code
good-cc1-exclude-list-request $validate-code
good-cc1-import-request $validate-code
good-cc1-isa-request $validate-code
good-cc2-all-request $validate-code
good-cc2-enumerated-request $validate-code
good-cc2-exclude-filter-request $validate-code
good-cc2-exclude-import-request $validate-code
good-cc2-exclude-list-request $validate-code
good-cc2-import-request $validate-code
good-cc2-isa-request $validate-code
good-coding-all-request $validate-code
good-coding-enumerated-request $validate-code
good-coding-exclude-filter-request $validate-code
good-coding-exclude-import-request $validate-code
good-coding-exclude-list-request $validate-code
good-coding-import-request $validate-code
good-coding-isa-request $validate-code
good-scd-all-request $validate-code
good-scd-enumerated-request $validate-code
good-scd-exclude-filter-request $validate-code
good-scd-exclude-import-request $validate-code
good-scd-exclude-list-request $validate-code
good-scd-import-request $validate-code
good-scd-isa-request $validate-code
icd-11 icd-11

ICD-11 Test Cases. See tests/icd-11/doco.txt for what these assert and why several of them are expected to fail against the current ICD-API.

term-caps $term-caps

Check that the minimum expected things are found in the server TerminologyCapabilities for ICD-11 servers

lookup-mms-code $lookup

Look up an MMS stem code by its short code, restricting the returned properties with the property parameter

lookup-mms-uri $lookup

The full entity URI is not a code in the MMS (the code is the bare entity id), so it is not found

lookup-mms-id $lookup

The same concept addressed by its entity id (the code) must give the same answer

lookup-mms-grouper $lookup

Look up a chapter (a grouper that does have a short code)

lookup-mms-no-code $lookup

A concept with an entity id but no short code must be marked not-selectable

lookup-mms-residual $lookup

Look up a residual category - the id is derived from the parent, the code ends in Y

lookup-mms-fr $lookup

Look up with displayLanguage - display and designations come back in French

lookup-icf-code $lookup

The same foundation entity in ICF carries a different short code

lookup-foundation $lookup

Look up a Foundation entity - full URI only, there are no short codes

lookup-bad-code $lookup

An unknown code is an error

lookup-bad-system $lookup

An unknown code system is an error

lookup-bad-version $lookup

An unknown version is an error

lookup-foundation-bare $lookup

A bare numeric id is not a Foundation code (WHO decision - the full URI is required)

lookup-foundation-residual $lookup

Residual categories exist only in the linearizations, not in the Foundation

lookup-bad-language $lookup

An unknown display language must be reported, not silently replaced by English

lookup-mms-zxx $lookup

$lookup with a valid displayLanguage that ICD-11 has no content in and never will (zxx, No linguistic content): the English display, and a warning that the default language was used

lookup-pc-simple $lookup

Look up a postcoordinated expression in short-code form

lookup-pc-breast $lookup

Look up 2090549892/unspecified&271422288&831985561 (Invasive carcinoma of breast, unspecified, left, breast): one postcoordination property per axis the stem declares, with the values on laterality and specificAnatomy

lookup-pc-breast-no-metadata $lookup

Without post-coordination-metadata: only the two valued axes, each with just its axis and value - no required, allowMultipleValues or valueSet, and no unvalued axes

lookup-pc-uri-form $lookup

An expression written with full entity URIs (and spaces) is not a code in the MMS, so it is not found

lookup-pc-id-form $lookup

The same expression written with entity ids (the code form, no spaces) must give the same concept

lookup-pc-residual-id $lookup

An expression whose stem is a residual, written with entity ids: the /other in 344162786/other is part of the id, the next / is a cluster separator

lookup-pc-cluster $lookup

A cluster expression: two stems joined by /, each with its own & extensions

lookup-pc-cluster-properties $lookup

The cluster of lookup-pc-cluster with the stem, id and postcoordinationValues properties requested: which value went on which axis of which stem

lookup-pc-cluster-medication $lookup

A second cluster with properties: DA42.83&XM3973/PB28&XM7YD4, where both stems take a value on the medication axis

lookup-pc-injury-fall $lookup

Look up an injury with laterality and type, clustered with its external cause (a fall, place and object): NA00.2&XK8G&XJ9NV/PG50&XE3HC&XE266

lookup-pc-injury-fall-no-metadata $lookup

With post-coordination-metadata=false: as without it - the valued axes only, and the cluster member PG50 carries only its own valued axes

lookup-pc-retinopathy $lookup

Look up 5A11/9B71.00&XS25&XK9K/9B71.00&XS5W&XK8G (type 2 diabetes; nonproliferative diabetic retinopathy, severe, right; and again, mild, left), written as entity ids: the same cluster member twice with different qualifiers is two values, each carrying its own qualifiers

lookup-pc-pneumonia-cluster $lookup

Look up a cluster of three stem codes: CA40.00/MG51.00/1B10.0

lookup-pc-pneumonia-cluster-no-metadata $lookup

Without post-coordination-metadata: the cluster members, which have no qualifiers, are just their Codings

lookup-pc-repeated-value $lookup

A value repeated on two different axes must not be silently dropped - the code that comes back must be the code that was asked about

lookup-pc-nondisjoint $lookup

Values on two axes drawing from overlapping value sets must each stay on their own axis

lookup-pc-invalid-axis $lookup

A value that is on no suggested axis of the stem must say so, not just 'not found'

lookup-pc-other $lookup

'Other' postcoordination: a value outside the stem's declared scales (unresolved - see doco.txt)

lookup-icf-pc $lookup

ICF postcoordination - every property returned must actually carry a value

lookup-icf-pc-old $lookup

The pre-2026 ICF postcoordination syntax is no longer valid

cs-validate-good $cs-validate-code

Validate a good code with no display

cs-validate-good-display $cs-validate-code

Validate a good code with the right display

cs-validate-display-case $cs-validate-code

Validate a good code with the right display in the wrong case: display matching is not case sensitive, so the code is valid with no display issue

cs-validate-coding-cc-good $cs-validate-code

A Coding with the classificationCode extension: the extension is right for the entity id: valid, and the coding is otherwise as cs-validate-id

cs-validate-coding-cc-pc $cs-validate-code

A Coding with the classificationCode extension: the extension carries the short-code form of a postcoordinated expression given in id form: valid

cs-validate-coding-cc-wrong $cs-validate-code

A Coding with the classificationCode extension: the extension has the wrong short code (1A01 is not the classification code of 257068234): an error

cs-validate-coding-cc-no-short $cs-validate-code

A Coding with the classificationCode extension: the extension is on a grouper that has no short code (its code range is not one): an error

cs-validate-coding-cc-short $cs-validate-code

A Coding with the classificationCode extension: the extension is on a coding whose code is already the short code - it is only used with an entity id: an error

cs-validate-coding-cc-icf $cs-validate-code

A Coding with the classificationCode extension: on an ICF coding, where it is defined as for the MMS - correct for the entity id: valid

cs-validate-coding-cc-foundation $cs-validate-code

A Coding with the classificationCode extension: on a Foundation coding - the Foundation has no classification codes, so the extension is not defined there: an error

cs-validate-bad-display $cs-validate-code

A wrong display must come back with issues and a message, not a bare result=false

cs-validate-bad-code $cs-validate-code

An unknown code must come back with issues and a message

cs-validate-case $cs-validate-code

ICD-11 codes are case sensitive, so a lower case code is not a code (note that WHO declares caseSensitive=false, which is the part that is wrong)

cs-validate-lang $cs-validate-code

A display that is right in another language is still wrong for the language that was asked for - the same as validation/simple-coding-bad-language

cs-validate-pc $cs-validate-code

Validate a postcoordinated expression

cs-validate-pc-injury-fall $cs-validate-code

Validate an injury with laterality and type, clustered with its external cause (a fall, place and object): NA00.2&XK8G&XJ9NV/PG50&XE3HC&XE266

cs-validate-pc-retinopathy $cs-validate-code

Validate 5A11/9B71.00&XS25&XK9K/9B71.00&XS5W&XK8G (type 2 diabetes; nonproliferative diabetic retinopathy, severe, right; and again, mild, left), written as entity ids: valid, and not in normal form - the two members are ordered by their qualifiers, and within each laterality comes before severity

cs-validate-pc-pneumonia-cluster $cs-validate-code

Validate a cluster of three stem codes: CA40.00/MG51.00/1B10.0

cs-validate-nf-normal $cs-validate-code

Normal form: NA00.2&XK8G&XJ9NV/PG50&XE3HC&XE266 written as entity ids - an expression already in normal form: no normalized-code, and its classificationCode is returned

cs-validate-nf-qualifier-order $cs-validate-code

Normal form: NA00.2&XJ9NV&XK8G written as entity ids - qualifiers out of order: the normal form puts them in the order the root defines its axes (laterality before typeOfInjury)

cs-validate-nf-same-axis $cs-validate-code

Normal form: 1A00&XN62R&XN8P1 written as entity ids - two qualifiers on the same axis (infectiousAgent): sorted by entity id, as strings

cs-validate-nf-member-order $cs-validate-code

Normal form: CA40.00/1B10.0/MG51.00 written as entity ids - cluster members out of order: MG51.00 is on the associatedWith axis of the root and comes first; 1B10.0 is on no axis of the root and comes after

cs-validate-nf-member-qualifiers $cs-validate-code

Normal form: NA00.2&XK8G&XJ9NV/PG50&XE266&XE3HC written as entity ids - the qualifiers of a cluster member out of order: sorted by the axes of the member, and they stay with the member

cs-validate-nf-binding-a $cs-validate-code

Normal form: 1D01.0Y/1G41/1G40 written as entity ids - 1G41 and 1G40 both fit hasManifestation and hasCausingCondition: binding in id order makes the normal form independent of the order written (see -binding-b)

cs-validate-nf-binding-b $cs-validate-code

Normal form: 1D01.0Y/1G40/1G41 written as entity ids - the same members as -binding-a written the other way round: the same normal form

cs-validate-nf-duplicate-qualifier $cs-validate-code

Normal form: 1A00&XN8P1&XN8P1 written as entity ids - a qualifier given twice: the duplicate is deleted

cs-validate-nf-duplicate-member $cs-validate-code

Normal form: CA40.00/MG51.00/MG51.00 written as entity ids - a cluster member given twice: the duplicate is deleted

cs-validate-nf-not-duplicate $cs-validate-code

Normal form: NA00.2/PG50&XE266/PG50&XE3HC written as entity ids - the same member twice with different qualifiers is two members, not a duplicate: both are kept, ordered by their qualifiers

cs-validate-nf-syntax-kept $cs-validate-code

Normal form: 1A00/XN8P1 written as entity ids - a value written as a cluster member: the normal form does not change / into &, so this is already normal

cs-validate-nf-icf-dot $cs-validate-code

Normal form: d5409.qp3 written as entity ids - the ICF dot qualifier stays a dot in the normal form

cs-validate-nf-axis-not-multiple $cs-validate-code

Normal form: NA00.2&XK8G&XK9J written as entity ids - two values on an axis that takes one (laterality on NA00.2): the normal form as usual, and a warning

cs-validate-nf-short-codes $cs-validate-code

Normal form: NA00.2&XJ9NV&XK8G/PG50&XE266&XE3HC - out of order and in short codes: normalized-code is the id form in normal order

cs-validate-uri $cs-validate-code

Validate a code given as a full entity URI: not a code in the MMS

cs-validate-id $cs-validate-code

Validate a code given as its entity id: the normal form, so no normalized-code, and its classificationCode is returned

expand-pcs $expand

Expand a WHO postcoordination scale value set

expand-pcs-count $expand

count is declared in TerminologyCapabilities and must be honoured

expand-pcs-offset $expand

offset is declared in TerminologyCapabilities and must be honoured

expand-pcs-filter $expand

The text filter must be applied

expand-pcs-filter-code $expand

A text filter matches the start of a short code as well as titles: XN8 finds XN8KD and XN8P1, which no title contains

expand-pcs-fr $expand

displayLanguage is declared in TerminologyCapabilities and must be honoured

expand-bad-url $expand

An unknown value set is an error

expand-inline-vs $expand

A value set supplied inline on the request must be expanded

expand-adhoc-enum $expand

Expand a client-supplied value set enumerating MMS codes

expand-adhoc-enum-uri $expand

Expand a client-supplied value set enumerating full entity URIs: not codes in the MMS. The server may refuse to expand the value set (4xx), or expand it without the invalid code, saying the include referred to an invalid code in an expansion-issue (200)

expand-adhoc-enum-id $expand

Expand a client-supplied value set enumerating entity ids

expand-adhoc-isa $expand

Expand a client-supplied is-a filter, filter value as a short code

expand-adhoc-isa-uri $expand

Expand the same is-a filter with the filter value as a full entity URI: not a code in the MMS. The server may refuse to expand the value set (4xx), or expand it without the filter's codes, saying the filter referred to an invalid code in an expansion-issue (200)

expand-adhoc-isa-id $expand

Expand the same is-a filter with the filter value as an entity id - must be identical

expand-adhoc-bad-code $expand

A client-supplied value set naming a code that does not exist (XXXX9) - the same as simple-expand-enum-bad and overload expand-enum-bad. The server may refuse to expand the value set (4xx), or expand it without the invalid code, saying the include referred to an invalid code in an expansion-issue (200)

expand-pcs-uri-form $expand

The WHO postcoordination scale as a client-supplied value set, filter values as full entity URIs: not codes in the MMS. The server may refuse to expand the value set (4xx), or expand it without the filter's codes, saying the filter referred to an invalid code in an expansion-issue (200)

expand-pcs-id-form $expand

The WHO postcoordination scale as a client-supplied value set, filter values as entity ids

expand-pcs-code-form $expand

The same value set with filter values as short codes - must expand identically

vs-validate-in $validate-code

A code that is in a WHO postcoordination scale value set

vs-validate-out $validate-code

A code that is not in the value set must come back with issues and a message

vs-validate-adhoc $validate-code

A code that is in a client-supplied value set

vs-validate-adhoc-uri $validate-code

Validate the full entity uri of 1A00 against a value set that enumerates the short code 1A00: not a code in the MMS

vs-validate-adhoc-id $validate-code

Validate the entity id of 1A00 against a value set that enumerates the short code 1A00: a member, given in its normal form, so no normalized-code, and its classificationCode is returned

vs-validate-adhoc-out $validate-code

A code that is not in a client-supplied value set

vs-validate-coding-cc-good $validate-code

The same Coding validated against a value set of all of MMS, ICF and the Foundation: the extension is right for the entity id: valid, and the coding is otherwise as cs-validate-id

vs-validate-coding-cc-pc $validate-code

The same Coding validated against a value set of all of MMS, ICF and the Foundation: the extension carries the short-code form of a postcoordinated expression given in id form: valid

vs-validate-coding-cc-wrong $validate-code

The same Coding validated against a value set of all of MMS, ICF and the Foundation: the extension has the wrong short code (1A01 is not the classification code of 257068234): an error

vs-validate-coding-cc-no-short $validate-code

The same Coding validated against a value set of all of MMS, ICF and the Foundation: the extension is on a grouper that has no short code (its code range is not one): an error

vs-validate-coding-cc-short $validate-code

The same Coding validated against a value set of all of MMS, ICF and the Foundation: the extension is on a coding whose code is already the short code - it is only used with an entity id: an error

vs-validate-coding-cc-icf $validate-code

The same Coding validated against a value set of all of MMS, ICF and the Foundation: on an ICF coding, where it is defined as for the MMS - correct for the entity id: valid

vs-validate-coding-cc-foundation $validate-code

The same Coding validated against a value set of all of MMS, ICF and the Foundation: on a Foundation coding, where the extension is not defined: an error

expand-mms-total $expand

The number of codes in MMS 2026-01 is 37,211, the count from walking the native ICD-API (include=descendant from the 28 roots)

expand-icf-total $expand

The number of codes in ICF 2026-01

expand-foundation-total $expand

The number of entities in the Foundation 2026-01

expand-mms-extension-total $expand

The number of extension codes (the descendants of chapter X) in MMS 2026-01 is 17,752, the count from the native ICD-API: count=0 over a filter bigger than the expansion limit is answered by counting, not refused

expand-mms-medicaments-total $expand

The number of medicaments (the descendants of 1170065830) in MMS 2026-01 is 6,470: count=0 over a filter bigger than the expansion limit is answered by counting, not refused

lookup-mms-chapter-x $lookup

A chapter root: chapter X (Extension Codes), with no parent and its 14 children in order

lookup-mms-window $lookup

A window (a grouper that sits beside the blocks): Sexually transmissible viral hepatitis

lookup-mms-large-parent $lookup

The parent with the most children (299): every child, in order, so the first and last are both checked

lookup-mms-deepest $lookup

One of the deepest concepts (depth 10, an extension code): XA3F65 Superior gastric lymph node

lookup-mms-residual-unspecified $lookup

An unspecified residual (1A03.Z): lookup-mms-residual covers the other kind

lookup-mms-pc-scales $lookup

The stem with the most postcoordination axes (2C31, eight): each axis by its schema uri, with its value set, whether it is required, and whether it takes several values

lookup-mms-pc-scales-no-metadata $lookup

Without post-coordination-metadata: a plain concept has nothing on any axis, so no postcoordination properties at all

lookup-mms-pc-scales-required $lookup

A stem with a required postcoordination axis (1D01.0Y, hasCausingCondition): each axis with its value set, whether it is required, and whether it takes several values

lookup-mms-source $lookup

The link from an MMS entity back to the Foundation entity it came from, as a Coding

lookup-mms-source-details $lookup

source.details: the Foundation link, carrying what a $lookup of the Foundation entity returns - definition and parent as subproperties, and its designations

lookup-icf-source $lookup

The link from an ICF entity back to the Foundation entity it came from

lookup-mms-es $lookup

Look up 1A00 in Spanish: the display and the linearization name

lookup-mms-text $lookup

A concept carrying seven kinds of text (6E62.1): every designation kind the import keeps

lookup-foundation-multi-parent $lookup

A Foundation entity with nine parents (the Foundation is not a tree)

lookup-mms-foundation-only $lookup

A Foundation entity that is in no linearization (Imagining) is not a code in MMS

subsumes-chapter $subsumes

Chapter 01 subsumes 1A00, several levels down

subsumes-subsumed-by $subsumes

1A00 is subsumed by its block, Bacterial intestinal infections

subsumes-unrelated $subsumes

1A00 and XN8P1 are in different chapters: not subsumed

translate-ciel1 $translate feature: translate

Test Translation Map using classificationCode based expressions

translate-ciel1a $translate feature: translate

Test Translation Map using a different classificationCode based expression

translate-ciel2a $translate feature: translate

Test Translation Map for icd-11 to ciel passing a classificationCode when the map has a classificationCode

translate-ciel2b $translate feature: translate

Test Translation Map for icd-11 to ciel passing a code when the map has a classificationCode: no match - the map's own codes are not normalised

translate-ciel3a $translate feature: translate

Test Translation Map for icd-11 to ciel passing a code when the map has a code

translate-ciel3b $translate feature: translate

Test Translation Map for icd-11 to ciel passing a classificationCode when the map has a code: matches through the normal form of the code passed

translate-ciel4 $translate feature: translate

Test Translation Map for ciel to icd-11 where the map's target is not a valid ICD-11 expression: the match is returned as the map has it, with an error saying the target code is not valid

regex-bad general

Bad Regex - checking defences against denial of service attack. These are unusual because servers have the option to succeed, or to refuse the request

expand-regex-bad $expand

Check expand is safe from catastrophic regex

validate-regex-bad $validate-code

Check validate is safe from catastrophic regex

expand-regex-bad-2 $expand

Check expand is safe from catastrophic regex

validate-regex-bad-2 $validate-code

Check validate is safe from catastrophic regex

related2 tx.fhir.org

Tests for $compare operation - comparing two value sets to determine their relationship (equivalent, subset, superset, overlap, disjoint, unknown)

related-eq-identical-def $compare

Equivalent: identical is-a filter definitions

related-eq-enum-reorder $compare

Equivalent: same enumerated codes in different order

related-eq-multi-include-reorder $compare

Equivalent: multiple includes from same system in different order

related-eq-filter-vs-enum $compare

Equivalent: is-a filter vs explicit enumeration of same codes

related-eq-import-vs-inline $compare

Equivalent: imported value set vs same definition inline

related-eq-import-reorder $compare

Equivalent: child value sets imported in different order

related-expeq-exclude-vs-enum $compare

Equivalent (expansion): all CS1 minus C vs enumeration of same codes

related-expeq-exclude-partial $compare

Equivalent (expansion): is-a root minus {A2,B2} vs enumeration of result

related-sub-branch-vs-root $compare

Subset: is-a A is subset of is-a root

related-sub-enum-vs-filter $compare

Subset: enumerated {A1,A2} is subset of is-a A

related-sub-base-vs-import-plus $compare

Subset: base VS is subset of VS that imports it and adds codes

related-sub-leaf-vs-subtree $compare

Subset: single leaf {A1} is subset of is-a A

related-super-root-vs-branch $compare

Superset: is-a root is superset of is-a A

related-expsub-exclude-narrower $compare

Subset (expansion): all minus {C,B1,B2} subset of all minus {C}

related-disj-diff-systems $compare

Disjoint: value sets from entirely different code systems

related-disj-diff-branches $compare

Disjoint: non-overlapping branches (A vs B) in same system

related-disj-enum-no-intersection $compare

Disjoint: enumerated codes with no intersection (flat system)

related-disj-multi-system $compare

Disjoint: multi-system value sets with no overlap

related-ov-enum-partial $compare

Overlap: partially overlapping enumerations

related-ov-filter-vs-enum $compare

Overlap: is-a A overlaps with enum {A2, B1}

related-ov-multi-include-partial $compare

Overlap: multi-include with partial overlap (is-a A+{B1} vs is-a B+{A1})

related-ov-import-partial $compare

Overlap: imported value sets creating partial overlap

related-ov-cross-system $compare

Overlap: cross-system partial overlap

related-ov-exclude-partial $compare

Overlap (expansion): overlap after excludes applied

related-unk-snomed-both-filter $compare

Unknown: two SNOMED is-a filters, can't determine relationship

related-unk-snomed-filter-vs-enum $compare

Unknown: SNOMED is-a filter vs enumerated SNOMED code

related-unk-unknown-system $compare

Unknown: unknown code system, can't expand

related-ver-same-def-diff-cs-version $compare

Version: same is-a A definition, CS1 v1 subset of CS1 v2

related-ver-all-diff-cs-version $compare

Version: all CS1, v1 subset of v2

related-ver-branch-diff-cs-version $compare

Version: is-a B, CS1 v1 subset of CS1 v2

related-ver-unversioned-vs-pinned $compare

Version: unversioned is-a A (uses latest=v2) superset of v1-pinned

related-ver-same-vs-diff-version $compare

Version: same VS URL, v1 subset of v2 (definition changed)

related-ver-import-version-cascade $compare

Version: import of v1-pinned VS subset of import of v2-pinned VS

langcodes tx.fhir.org

IETF language code (BCP-47) test cases

validate-lang-base $cs-validate-code

a bare language subtag is valid (en)

validate-lang-region $cs-validate-code

language plus an ISO 3166 region (en-US)

validate-lang-script $cs-validate-code

language plus a script (zh-Hans)

validate-lang-script-region $cs-validate-code

language, script and region together (zh-Hans-CN)

validate-lang-region-private $cs-validate-code

a region inside the QM..QZ private-use range - the registry writes those as a range rather than one entry per code (en-QM)

validate-lang-grandfathered $cs-validate-code

a grandfathered tag: registered whole, and it does not decompose into valid subtags (i-klingon)

validate-lang-base-bad $cs-validate-code

two letters that are not an allocated language (zz)

validate-lang-region-bad $cs-validate-code

two letters that are neither allocated nor inside a private-use range (en-AB)

validate-lang-script-bad $cs-validate-code

four letters that are not an allocated script (en-Abcd)

validate-lang-extlang-prefix-bad $cs-validate-code

the extlang cmn carries Prefix: zh in the registry, so it may not follow en (en-cmn)

validate-lang-variant-prefix-bad $cs-validate-code

the variant 1901 carries Prefix: de in the registry, so it may not follow en (en-1901)

validate-lang-case-language $cs-validate-code

the language subtag written in the wrong case (EN): valid, because BCP 47 tags are case-insensitive, but the server returns normalized-code en and notes the difference

validate-lang-case-region $cs-validate-code

the region subtag written in the wrong case (en-us): valid, because BCP 47 tags are case-insensitive, but the server returns normalized-code en-US and notes the difference

validate-lang-case-all $cs-validate-code

every subtag written in the wrong case (ZH-hans-cn): valid, because BCP 47 tags are case-insensitive, but the server returns normalized-code zh-Hans-CN and notes the difference

subsumes-lang-base-region $subsumes

en subsumes en-US: a region added to a bare language

subsumes-lang-reverse $subsumes

en-US is subsumed by en

subsumes-lang-equivalent $subsumes

a tag against itself

subsumes-lang-script $subsumes

zh subsumes zh-Hans-CN: script and region added

subsumes-lang-skipped-script $subsumes

en-US subsumes en-Latn-US, though the added script sits between the two subtags en-US names - RFC 4647 extended filtering rather than basic

subsumes-lang-variant $subsumes

de subsumes de-1901: a variant added

subsumes-lang-siblings $subsumes

en-US and en-GB: two regions of one language, neither subsumes the other

subsumes-lang-scripts $subsumes

zh-Hant and zh-Hans-CN: different scripts

subsumes-lang-crossed $subsumes

en-Latn and en-US: each states something the other does not

subsumes-lang-unrelated $subsumes

en and fr: different languages

subsumes-lang-case $subsumes

EN subsumes en-us: BCP 47 tags are case-insensitive

subsumes-lang-grandfathered $subsumes

zh does not subsume zh-min-nan: a grandfathered tag is matched whole and has no components to compare

validate-lang-filter-language-in $validate-code

a code in a language=en filter

validate-lang-filter-language-out $validate-code

a code with a different language

validate-lang-filter-region-in $validate-code

a code in a region=US filter, whatever its language

validate-lang-filter-region-out $validate-code

a code with a different region

validate-lang-filter-both-in $validate-code

language and region both fixed: the script is free to vary

validate-lang-filter-both-out $validate-code

the language matches but the region does not, and the message says which rule failed

validate-lang-filter-script-in $validate-code

a script filter validates codes even though it cannot be expanded

validate-lang-filter-script-out $validate-code

a code in a different script

validate-lang-filter-language-bare $validate-code

the bare language itself is in a language=en filter: a language filter matches the language, however much or little else the tag says

validate-lang-filter-region-absent $validate-code

a tag with no region at all is not in a region=US filter: an absent component does not match a fixed one

validate-lang-filter-script-absent $validate-code

a tag with no script at all is not in a script=Latn filter, even though Latn is the script English is written in

validate-lang-filter-both-absent $validate-code

the language matches but there is no region to match, so the code is not in the value set

expand-lang-language $expand

a fixed language expands to its regions (and the bare language), paged

expand-lang-both $expand

language and region fixed expands to the scripts, starting with the tag that has none

expand-lang-region $expand

a fixed region is finite but far too large to expand, so it answers too-costly. The header sets the limit, so that every server, whatever its own limit, exercises the same path

expand-lang-script $expand

a script alone leaves the language open, so there is nothing to enumerate

expand-langcodes-all $expand

Tests the $expand operation for all language codes (a special case): the grammar is unbounded, so the common-languages base value set is returned, marked as an incomplete (unclosed) expansion

ecosystem tx.fhir.org

Value sets whose code systems are spread across more than one server in the ecosystem, so that no single server holds them all: tx.fhir.org answers for them by asking the other servers

ecosystem-cz-in $validate-code

A Czech edition code in the value set (is-a 46635009)

ecosystem-cz-excluded-code $validate-code

A Czech edition code that the value set excludes by code

ecosystem-cz-excluded-filter $validate-code

A Czech edition code that the value set excludes by filter (is-a 70694009)

ecosystem-ee-in $validate-code

An Estonian edition code in the value set (is-a 49436004)

ecosystem-ee-excluded-code $validate-code

An Estonian edition code that the value set excludes by code

ecosystem-ee-excluded-filter $validate-code

An Estonian edition code that the value set excludes by filter (is-a 282825002)

ecosystem-cc-cz-in-ee-out $validate-code

A CodeableConcept with a Czech code in the value set and an Estonian code excluded from it: the Czech code meets the binding

ecosystem-cc-cz-out-ee-in $validate-code

A CodeableConcept with a Czech code excluded from the value set and an Estonian code in it: the Estonian code meets the binding

ecosystem-cs-cz-good $cs-validate-code

A Czech edition code, validated against the code system (CodeSystem $validate-code, no value set)

ecosystem-cs-ee-good $cs-validate-code

An Estonian edition code, validated against the code system (CodeSystem $validate-code, no value set)

ecosystem-cs-cz-bad-code $cs-validate-code

A code that isn't in the Czech edition, validated against the code system (no value set)

ecosystem-cs-cz-bad-display $cs-validate-code

A Czech edition code with the wrong display, validated against the code system (no value set)

closure feature: closure sequential

$closure: build a closure table one concept at a time. The tests depend on each other, so the suite runs in order, on one thread, after all the other suites. The table is reset by the first test, and the code system it uses is only sent in that request

closure-init $closure

Initialise (reset) the closure table, supplying the code system it uses. The code system is only sent here: the server keeps it with the table

closure-add-code2a $closure

Add the first concept: nothing to relate it to yet

closure-add-code2aI $closure

Add a child of a concept already in the table

closure-add-code2 $closure

Add an ancestor of concepts already in the table, including a transitive one

closure-add-code1 $closure

Add a concept unrelated to anything in the table

closure-add-code2aII $closure

Add a concept below two concepts already in the table

closure-add-code2aI-again $closure

Add a concept that is already in the table: nothing changes, and the version does not move

closure-add-code2b $closure

Add a sibling of a concept already in the table: related to the parent only

closure-resync-2 $closure

Resynchronise from version 2: every entry added after it

closure-resync-0 $closure

Resynchronise from the start: the whole table

closure-dispose $closure

Inform the server that the closure table is no longer wanted, and can be deleted

icf icf

Tests for ICF (2001a) qualifiers: the .XYZ grammar (extent, nature, localization; 8 = not specified), the displays it generates, enumerated value sets with qualified codes, and value set filters that require or forbid qualifiers

icf-cs-plain $cs-validate-code

A plain category

icf-cs-extent $cs-validate-code

A body function with an extent qualifier

icf-cs-extent-0 $cs-validate-code

Extent 0 (no impairment)

icf-cs-extent-4 $cs-validate-code

Extent 4 (complete impairment)

icf-cs-extent-9 $cs-validate-code

Extent 9 (not applicable) is shown in the display

icf-cs-long-code $cs-validate-code

A qualifier on a 5 character category

icf-cs-three $cs-validate-code

A body structure with extent, nature and localization

icf-cs-two $cs-validate-code

A body structure with extent and nature

icf-cs-eights $cs-validate-code

All three qualifiers 8 (not specified): the display is just the category

icf-cs-eight-first $cs-validate-code

Extent 8 is silent, the nature after it is not

icf-cs-display-good $cs-validate-code

The right display for a qualified code

icf-cs-display-category $cs-validate-code

The category display is not the display of a qualified code

icf-cs-display-bad $cs-validate-code

A wrong display for a qualified code

icf-cs-display-eights $cs-validate-code

The category display is right when every qualifier is 8

icf-cs-bad-value $cs-validate-code

5 is not an extent value

icf-cs-too-many $cs-validate-code

No more than three qualifiers

icf-cs-not-digits $cs-validate-code

Qualifiers are digits

icf-cs-empty $cs-validate-code

A . with no qualifiers after it

icf-cs-heading-chapter $cs-validate-code

A chapter cannot be qualified

icf-cs-heading-block $cs-validate-code

A block cannot be qualified

icf-cs-unknown-category $cs-validate-code

An unknown category with qualifiers is an unknown code

icf-cs-b-too-many $cs-validate-code

A body function takes one qualifier only

icf-cs-d-performance $cs-validate-code

An activity with a performance qualifier

icf-cs-d-two $cs-validate-code

An activity with performance and capacity

icf-cs-d-four $cs-validate-code

An activity with all four qualifiers: performance, capacity, capacity with assistance, performance without assistance

icf-cs-d-eights $cs-validate-code

Performance and capacity not specified (8), with the optional third and fourth qualifiers

icf-cs-d-too-many $cs-validate-code

An activity takes no more than four qualifiers

icf-cs-d-bad-capacity $cs-validate-code

5 is not a capacity value

icf-cs-e-barrier $cs-validate-code

An environmental factor that is a barrier

icf-cs-facilitator $cs-validate-code

An environmental factor that is a facilitator: + in place of the .

icf-cs-e-no-facilitator $cs-validate-code

No facilitator (+0)

icf-cs-e-barrier-nine $cs-validate-code

Not applicable is written .9

icf-cs-e-facilitator-eight $cs-validate-code

A facilitator, extent not specified: 8 is silent in the display

icf-cs-e-facilitator-nine $cs-validate-code

A facilitator has no 9 (not applicable is .9)

icf-cs-e-two $cs-validate-code

An environmental factor takes one qualifier only

icf-cs-b-facilitator $cs-validate-code

Only an environmental factor can be a facilitator

icf-vs-enum-plain $validate-code

A plain code listed in an enumerated value set

icf-vs-enum-qualified $validate-code

A qualified code listed in an enumerated value set. The code has no version: ICF says versionNeeded = true, so there's a warning, even though the value set pins the version

icf-vs-enum-eights $validate-code

A qualified code (all 8) listed in an enumerated value set

icf-vs-enum-other-qualifier $validate-code

An enumerated value set has only the qualified codes it lists

icf-vs-enum-unlisted-eights $validate-code

An unlisted qualified code is not in an enumerated value set, even when it says no more than a listed one

icf-vs-all-plain $validate-code

A plain code in an is-a value set. The code has no version: ICF says versionNeeded = true, so there's a warning, even though the value set pins the version

icf-vs-all-qualified $validate-code

A qualified code is in an is-a value set when its category is

icf-vs-all-other-component $validate-code

A qualified code is not in an is-a value set when its category is not

icf-vs-extent-req-good $validate-code

Extent required: present

icf-vs-extent-req-nine $validate-code

Extent required: 9 (not applicable) counts as present

icf-vs-extent-req-plain $validate-code

Extent required: a plain code

icf-vs-extent-req-eight $validate-code

Extent required: 8 does not count

icf-vs-extent-req-heading $validate-code

Extent required: a heading cannot have an extent, so is not in the value set

icf-vs-full-good $validate-code

All three required: present

icf-vs-full-missing $validate-code

All three required: localization missing

icf-vs-full-eight $validate-code

All three required: localization 8 does not count

icf-vs-full-nature-eight $validate-code

All three required: nature 8 does not count

icf-vs-full-plain $validate-code

All three required: a plain code

icf-vs-noloc-plain $validate-code

No localization: a plain code

icf-vs-noloc-two $validate-code

No localization: two qualifiers

icf-vs-noloc-eight $validate-code

No localization: localization 8 is allowed

icf-vs-noloc-present $validate-code

No localization: localization present

icf-vs-capacity-good $validate-code

Capacity required: present

icf-vs-capacity-performance-only $validate-code

Capacity required: performance only

icf-vs-capacity-eight $validate-code

Capacity required: 8 does not count

icf-vs-capacity-plain $validate-code

Capacity required: a plain code

icf-vs-facilitator-good $validate-code

Facilitators: a facilitator

icf-vs-facilitator-barrier $validate-code

Facilitators: a barrier

icf-vs-facilitator-eight $validate-code

Facilitators: 8 does not count

icf-vs-facilitator-plain $validate-code

Facilitators: a plain code

icf-vs-noqual-plain $validate-code

No qualifiers: a plain code

icf-vs-noqual-qualified $validate-code

No qualifiers: a qualified code

icf-vs-noqual-eights $validate-code

No qualifiers: not even all 8

icf-expand-enumerated $expand

Expanding an enumerated value set with qualified codes gives their composed displays

icf-ec icf

Extension-codes supplements for ICF (2001a), whose qualified (post-coordinated) codes are a grammar: a supplement gives some of them human displays. In the icf mode, and a suite of its own, since its global supplement would change the icf suite's other tests

ec-icf-lookup-global $lookup

ICF: $lookup of a qualified (post-coordinated) code that a global extension-codes supplement gives a display: it has the supplement's display

ec-icf-lookup-local-referenced $lookup

$lookup of a qualified code that an extension-codes supplement that is not global gives a display, when the supplement is referenced: it has the supplement's display

ec-icf-lookup-local-unreferenced $lookup

The same when the supplement is not referenced: the display is the one generated from the category and qualifiers

ec-icf-validate-global $cs-validate-code

$validate-code of a qualified code that a global extension-codes supplement gives a display, with no display: the display is the supplement's

ec-icf-validate-global-display $cs-validate-code

The same code with the supplement's display: valid

ec-icf-validate-global-generated-display $cs-validate-code

The same code with the generated display: still valid, though the supplement's display is the one returned

ec-icf-validate-global-wrong-display $cs-validate-code

The same code with a different display: an error, as for a display the code system gives

ec-icf-validate-global-wrong-display-lenient $cs-validate-code

The same, with lenient-display-validation: a warning

ec-icf-validate-local-referenced $cs-validate-code

$validate-code of a qualified code that a referenced extension-codes supplement (not global) gives a display, with no display: the display is the supplement's

ec-icf-validate-local-referenced-wrong-display $cs-validate-code

The same code with a different display: valid, with a warning

ec-icf-validate-local-unreferenced $cs-validate-code

The same code with the supplement's display, when the supplement is not referenced: the supplement is not used, so its display is not a display of the code

ec-icf-expand $expand

$expand of a value set that lists qualified codes without displays: those the global supplement gives displays get them, the others get their generated displays

ec-icf-expand-referenced $expand

The same, with the supplement that is not global referenced: all four get the supplements' displays