Project Number Date
EtherCIS-VEHR-features 0 25 Jan 2018, 12:11

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 452ms 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
9s 612ms
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.
Given The server is running 4s 468ms
And The client system is logged into a server session 2s 348ms
And The openEHR template for the composition is available to the server 414ms
And An EHR is created 389ms
And A composition is persisted under the EHR 1s 688ms
Then An AQL query should return data from the composition in the EHR 303ms
After QueryWithAqlSteps.cleanUp() 015ms
2s 839ms
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.
Given The server is running 2s 302ms
And The client system is logged into a server session 053ms
And The openEHR template for the composition is available to the server 057ms
And An EHR is created 044ms
And A composition is persisted under the EHR without an EHR identifier 325ms
Then An AQL query should return data from the composition in the EHR 055ms
After QueryWithAqlSteps.cleanUp() 005ms