Data validation conformance tests for URI data types

The DV_URI and the DV_EHR_URI have a value attribute that should have a specific format, in both bases the value should be compliant with the RFC3986 URI definition, and for DV_EHR_URI the URI scheme should be equals to ehr.

Since DV_URI.value is String, in archetypes and templates it is possible to define a constraint using the C_STRING pattern or list constraints.

When using the pattern, we need to be sure the constraint is compatible with the URI format.

I couldn’t find this detail noted in the specs.

A related point, in the DV_URI there is no invariant / method to validate the value is compliant with RFC3986. I believe we might need something to check the value is correct. Any thoughts?

1 Like