Iteration 11 Requirements

Overall system functional requirements are documented on the Feature List wiki page.

Features from previous functionality cannot be lost.

System Non-Functional Requirements

• Processes 10,000 individual records in a timely manner (e.g. less than one hour running after practice hours)
• Alignment with PITO E2E-DTC version 1.3

OSCAR Component Requirements

OSCAR is the test EMR supported for this iteration.

Functional Requirements

1. From within an individual's chart, user can export an individual patient summary record
2. Outside of an individual chart, user can export individual patient summary documents for all patients as a batch
3. The scheduler module should be able to identify which records have been recently updated and only export those records

Non-Functional Requirements

1. Export format is HL7 CDA standard-based, specifically the "E2E" format created by the BC Physician Information Technology Office program.
2. For this iteration, E2E content sections must include all sections that are considered required for a minimally functional E2E document.
3. Export must perform in a timely manner - while a user waits (30 min / 11000 patients)
4. Export feature saves summary document(s) in a folder on the same workstation that the user initiated the request from.
5. Export format is customizable for users that adopt a different document standard.

hQuery Component Requirements

We assume that this wiki page only outlines new features for hQuery.

Non-Functional Requirements

1. Imports records in the E2E 1.3 patient summary document format.
2. All hQuery components are running on Ruby 1.9.3