https://github.com/dipsas/openehr-conformance

Documentation and examples related to the conformance on openEHR implementations.
https://github.com/dipsas/openehr-conformance

healthcare healthcare-application openehr openehr-standard

Last synced: about 1 month ago
JSON representation

Documentation and examples related to the conformance on openEHR implementations.

• Host: GitHub
• URL: https://github.com/dipsas/openehr-conformance
• Owner: DIPSAS
• License: apache-2.0
• Created: 2017-04-20T17:48:55.000Z (almost 9 years ago)
• Default Branch: master
• Last Pushed: 2020-01-24T12:06:35.000Z (about 6 years ago)
• Last Synced: 2025-06-05T05:24:38.688Z (9 months ago)
• Topics: healthcare, healthcare-application, openehr, openehr-standard
• Size: 186 KB
• Stars: 4
• Watchers: 2
• Forks: 1
• Open Issues: 0
• Metadata Files:
  • Readme: README.adoc
  • License: LICENSE

Awesome Lists containing this project

README

          
= OpenEHR Conformance

== Background 

This repository was created to collect some challenges we are facing when implementing an openEHR solution. We want to share the problems and the way we (DIPS AS) have solved them. By doing this the open way we want to contribute to a shared conformance on how to implement openEHR applications. 

== Areas 

* AQL 

* Exclusion

== AQL 

=== The permutation problem 

The first case added is the the permutation problem. The problem we have faced is how to interpret and create a resultset when EVENTS in an OBSERVATION is repeated. 

include::aql/case1-permutations/index.adoc[leveloffset=+2]

=== AQL on FOLDER 

AQL on FOLDER has some issues. In case 2 we have added some examples on how to query folders. 

include::aql/case2-folders/index.adoc[leveloffset=+2]

== Exclusion 

This is a description of the challenges with expressing the inclusion and exclusion pattern in a computable way.