Summary:

OSCAR and MyOSCAR have the capability of sharing information between the two disparate systems.  OSCAR is the main application for the clinics and MyOSCAR is the main application (PHR) for the demographics or end users of the system.  Depending on the level of access and sharing which both the demographic and care provider set and configure, will depend on what information will be shared and available between the two systems.

Purpose:

This Page is dedicated to the use cases and tests that will be available to the group in order to know what is expected when integrating between OSCAR and MyOSCAR.

Workflow:

Use case documents will be the parent to one or more test case documents within Confluence.  When creating test cases for OSCAR -> MyOSCAR integration here in confluence, make sure to keep the "Use case" -> "Test Case" hierarchy.  This will make it easy to search, access and manage the documents.HRM (Hospital Report Manager)

Purpose:

This document explains two areas of testing required for HRM: 1) Conformance and 2) Functionality of Reports to be consumed by your EMR offering. It also includes information specific for you to be used during Validation Testing. The validation process will be performed in an isolated non-Production environment where no PHI data is used. You may opt to start development as soon as this letter is received, or wait until your official engagement with the OntarioMD Validation Team. Conformance testing is to be executed in sequence; functionality testing will follow. You will be engaged by OntarioMD’s Validation team at which time a walk-through of the process will be scheduled. Support prior to this engagement will be limited.

Workflow:

Selenium IDE tests:

Every test case here will also have a corresponding test case or a set of test cases in Selenium IDE.  The Selenium test cases for OSCAR -> MyOSCAR integration are stored in /workspace/oscar/src/test/selenium/<test suite>/