Known Issues

Below are known issues impacting the generally available relational schema. Resolving these issues would constitute a breaking change, so Zus plans to address these issues in the next version of the relational schema.

The v2 schema resolves several of these issues. See the v1 to v2 migration guide for details.

Known issues:

For the LENS_ENCOUNTER table, the LENS_SNOMED_CONDITION_ID is mislabeled and does not link to the LENS_SNOMED_CONDITION table, but instead the normal CONDITION_TABLE.
- Resolved in v2: LENS_ENCOUNTER_DIAGNOSIS.LENS_SNOMED_CONDITION_ID is renamed to CONDITION_ID and links to the base CONDITION table.
In theLENS_TRANSITION_OF_CARE_DIAGNOSIS table, the column CONDITION_ID should be renamed to LENS_SNOMED_CONDITION_ID to better fit the schema naming convention.
- Resolved in v2: the column is renamed to LENS_SNOMED_CONDITION_ID.
The CONTACT_POINT table mixes data for both patients and practitioners, which some customers have found confusing. We may separate this out into two tables in future schema versions.
- Resolved in v2: CONTACT_POINT is removed. Its columns are now on each resource's <RESOURCE>_TELECOM table.
In the LENS_SNOMED_CONDITION, we may choose to remove the code_icd10cm column because Lens conditions can have multiple ICD-10 codes and there is not a single ICD-10 code that can represent the entire collection.
- Resolved in v2: CODE_ICD10CM is removed. Use LENS_SNOMED_CONDITION_CODE_CODING and filter for http://hl7.org/fhir/sid/icd-10-cm.
Customers have noted inconsistent use of “timestamp without timezone” and “timestamp with timezone” formatting for timestamp data types in the Zus relational schema.
- Resolved in v2: all timestamp columns are timestamp with timezone.

Related pages