Clarify specification of DV_EHR_URI scheme




Heath Frankel
December 10, 2015, 12:06 AM

The relative EHR URI examples should be as original suggested in the marked up change proposal document attached. Notice the lack of a leading slash after the scheme.

ehr:compositions/87284370-2D4B-4e3d-A3F3-F303D2F4F34B/content[openEHR-EHR-SECTION.vital_signs.v1]/items[openEHR-EHR-OBSERVATION.blood_pressure.v1]/data/events[at0006, 'any event']/data/items[at0004]


Heath Frankel
December 10, 2015, 12:52 AM

The note about support for ehr URIs of the form ehr:GUID is not correct, it isn't about the use of slash before an ehr_id but the need for an ehr_attribute_name before a version_locator. As indicated above, the need for a slash in the relative path example is actually wrong and was incorrectly transcribed from the original change proposal document attached .

I also don't think we should be encouraging backward compatibility in new systems, it should be existing systems that should be encouraged to support and upgrade existing URIs of to the new form. Ocean will also need to do this.

Thomas Beale
December 10, 2015, 10:05 AM

I have reverted to an earlier version of the texts that everyone accepted. The only changes to the data types now are fixed RFC links.

I also corrected the mix-transcribed leading slash in the relative URIs at the end.

Heath Frankel
December 10, 2015, 10:37 PM

Looking clean. There is just one hang over in the data types spec at the end of the first paragraph in section 10.4.1 which indicates the following syntax is represented as a Antlr parser rule (in brackets).

Thomas Beale
December 11, 2015, 8:59 AM

Fixed and uploaded (changes are now flowing on the master branch, use the links above to see resulting doc).



Rong Chen

Raised By

Thomas Beale


Affects versions