Below is some information about the value sets and code systems used in Trifolia exports.

Value Set Members

Trifolia treats value sets as though they are fully expanded.  When Trifolia presents a value set that contains another value set, it displays all the members of the value set in an expanded view. This represents a fully expanded view of the value set.

Value Set Status & Date

Each member of a value set contains status and date fields. Date and Status fields are used to determine which members will be exported to XML and MS Word output.

Calculated Date

For each member of a value set, a date is calculated, and this date, along with the status determines whether to include that member in an export. The date is derived using this priority:

  1. If the constraint includes a value set binding date, it is used.
  2. If no value set binding date is present, the implementation guide's publish date is used.
  3. If no implementation guide publish date is available, the XML or MS Word export date is used.

Status

The value set member status can be entered when a new value set member is added.  Once the date is calculated, the status (if entered) and date are used to determine whether the member is included in the export as follows:

  • The member is included in the export if the status is Unspecified (empty) or the calculated date is prior to the date for the member's active status.
  • The member is excluded from the export the calculated date falls on or after the member's Inactive status date.

Example

Given the following value set:

Code

Display Name

Code System

Status

Date

Value 1

Display 1

SNOMED

Unspecified (blank)

Unspecified

Value 2

Display 2

LOINC

Active

1/1/2013

Value 3

Display 3

SNOMED

Active

1/1/2013

Value 2

Display 2

LOINC

Inactive

3/1/2013


For an export generated on 1/15/2013, the resulting list is:

  • Value 1
  • Value 2
  • Value 3

For an export generated on 5/1/2013, the resulting list is:

  • Value 1
  • Value 3

Code Systems and Value Sets

Trifolia creates a relationship between a code system and a value set member. Code systems are used to reference a name/identifier combination.

A code system is referenced in one of the following ways:

  • A value set’s member is a member of a specified code system
  • A constraint indicates that an element/attribute in a template/profile must be selected from a code system
  • A constraint, in combination with the constraint value, indicates that the value is a member of a specified code system

Vocabulary XML

Vocabulary XML is used for Schematron validation. Value sets are bound to constraints in the Template Editor.  Only a value set with a Binding value of static is validated by the Schematron.  When you export vocabulary XML, only a value set with a Binding value of static is included. A value set with a Binding value of unspecified (empty) or dynamic is ignored.  For more information on binding value sets see Bindings in the Constraints section.