Project Number Date
EtherCIS-VEHR-features 0 30 Jan 2018, 15:17

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Provide VEHR API access via REST calls 12 0 0 0 0 12 2 0 2 12s 186ms Passed
Feature Provide VEHR API access via REST calls
In order to work with openEHR data As a client system I want to make REST API calls over http
7s 349ms
template is in place and the user is logged in.
Given The server is running 4s 279ms
And The client system is logged into a server session 2s 344ms
And The openEHR template prescription.opt for the composition is available to the server 409ms
And An EHR is created 314ms
2s 124ms
Query openEHR data using the Archetype Query Language. openEHR data and an openEHR template that allows validation of the data should exist on the server before it can be queried. openEHR data should be stored under an EHR. The AQL query should be provided as a parameter to the REST API and results should be returned in a form compatible with the AQL results specification.
When A composition is persisted under the EHR 1s 810ms
Then An AQL query should return data from the composition in the EHR 314ms
After QueryWithAqlSteps.cleanUp() 019ms
After CompositionAPISteps.cleanUp() 000ms
2s 331ms
template is in place and the user is logged in.
Given The server is running 2s 109ms
And The client system is logged into a server session 061ms
And The openEHR template prescription.opt for the composition is available to the server 088ms
And An EHR is created 071ms
380ms
Same scenario as 'Query openEHR data using AQL over REST' but the server is not provided the ehr identifier for the composition commit. Instead it uses the session Id to find the target ehr id.
When A composition is persisted under the EHR without an EHR identifier 332ms
Then An AQL query should return data from the composition in the EHR 047ms
After QueryWithAqlSteps.cleanUp() 011ms
After CompositionAPISteps.cleanUp() 000ms