workshop-openehr Works

Your post is the first one for OpenEHR, well done!

I also struggled with the fact that the iris.script has errors like:

1. ##class(Security.Applications).Import() needs to be executed in %SYS
2. No error handling so no way to notice it failed
3. No halt at the end

I also enabled syntax highlighting via settings.json

I wonder why ehr_id is considered a numeric, by default these are usually GUIDs.

The compositionUid field is too short for a normal openEHR. document uid which could be something like "bcfc0ce6-5264-44a0-cfa5-0fc79e271f7b::local.ehrbase.org::1".

The REST API method did not to set the content-type, which leaves the output unformatted.

The spanish output was not helpful for me. Did you translate the messages in the openehr-validator, or how did you manage that?

I found that the approach to querying that you use is too static. When I store in a Vital Signs Composition, the query engine doesn't find it, because it hjs no SECTON layer. I guess the approach to finding CSV's on just the archetype name is not fine-grained enough...

Since last September I have worked an OpenEHR project that implements the complete OpenEHR API, but currently has only a subset of the AQL support. At the same time, it does support search on value in the document using a special index.

Are you open to combining the strength?

Thanks,

Theo