Skip to content

3.0.0

Compare
Choose a tag to compare
@mikix mikix released this 10 Jun 13:40
· 32 commits to main since this release
4202f80

Breaking changes since 2.0.0:

  • c_us_core_v4_count: The existing per-profile tables have all been split in two: a _mandatory table and a _must_support table.
    • The valid_mandatory and valid fields have been removed from the must-support table and the mandatory table now lists each separate mandatory check.
    • When running in cube mode (the default), the observation mandatory tables are also broken up into two or three smaller tables for performance reasons (_mandatory1, _mandatory2, etc). This is not elegant, but the observation table is a big beast and cubing wouldn't complete on a large database if we don't do this. aggregate mode keeps all the fields in one table.
    • Any duplicated checks between mandatory and must-support profiles are not included in the mandatory table, to avoid duplicate field names and the resulting confusion. For example, Condition's must-support verificationStatus field's value is both (a) checked for validity against the required binding as a mandatory check and (b) checked for whether it is present (and also checked for a valid value) as a must-support check. That's redundant in a c_us_core_v4_count context, so we only track valid_verification_status in the must-support table.
  • c_us_core_v4_count: Encounter's must-support valid_reason_code field has been renamed to valid_reason as it now also checks the alternative field reasonReference (in addition to reasonCode)

Other import changes:

  • c_us_core_v4_count: Encounter's must-support valid_location field also checks the alternative field serviceProvider (in addition to location.location)
  • q_system_use: Allow the NullFlavor system for DocumentReference's type field
  • q_system_use: Correct a few typos on Procedure's code field's allowed systems
  • q_system_use: If a field is not present, we don't include it in the numerator (this avoids erroneously including Vital Signs that don't have a valueCodeableConcept field). If a required field is missing altogether, that's another metric's job - this metric just flags the systems in use.