LOCATABLE REF and EHR URI

Implementers (archive)
1

Looking at the Locatable Ref class: http://openehr.org/releases/1.0.2/architecture/rm/support_im.pdf

The as_uri function of LOCATABLE_REF is defined to return the following: “ehr://” + id.value + “/” + path

If we read Architecture Overview: http://openehr.org/releases/1.0.2/architecture/overview.pdf at page 64.

The EHR scheme is defined as: ehr:ehr_locator/top_level_structure_locator/path_inside_top_level_structure

We get a little confused and think one of them is wrong.

I we define the following:

a = ehr_locator

b = top_level_structure_locator

c = path_inside_top_level_structure

Given the support_im definition we get the following allowed EHR uris:

ehr:/ a / b / c

ehr:/a/b

ehr://b/c

And given the architecture overview we get the following allowed uris:

ehr: a / b / c

ehr:a/b

ehr:/b/c

Which one is correct?

Could they both be correct? If yes – please explain.

Vennlig hilsen
Bjørn Næss
Produktansvarlig
DIPS ASA

Mobil +47 93 43 29 10

2

Hi Bjørn,

It should be ehr: not ehr://. That correction was given to me by Tim Berners-Lee himself, so I guess it's correct.

- thomas

(attachments)

oceanfullsmall.jpg
btnliprofileblue80x15.png

3

Thanks.

This means we should update the http://openehr.org/releases/1.0.2/architecture/rm/support_im.pdf

The ‘as_uri’ function of LOCATABLE_REF should be changed:

(attachments)

oceanfullsmall.jpg
btnliprofileblue80x15.png

4

Hi Bjorn,

There are significant issues with the ehr URI and I have raised a number for issues in Jira. Hopefully this will be one of the first things that will be looked at now that there is some intent to make progress on the specifications.

Having said that, at a high level, I agree with your suggested relative URI syntax if you are assuming id.value is the composition uid and not the ehr_id.

Heath

(attachments)

oceanfullsmall.jpg
btnliprofileblue80x15.png