|OIO System (OIO on Zope):|
Flexible and Secure Information System for Clinicians and Researchers
Open Infrastructure for Outcomes (OIO) system enables clinicians, researchers, and other non-programmers to create and maintain flexible
and portable patient/research records.
It aims to achieve the
" of data portablity as elegantly described by
John G. Faughnan.
The major components of the OIO system
are the web-accessible OIO Server and OIO Library.
is a highly flexible web-based data management system
that manages users, patients, and information about patients.
(Of course, the same system can just as easily manage information about
customers, invoices, shipments, and accounts.)
is a metadata repository that facilitates the sharing
of metadata (e.g. plug-and-play web-forms, project descriptions)
between users and between OIO Servers.
Library also hosts a public/open content database of open source
medical software projects and related documents.
[Jump to Brief summary with screenshots]
Users of the OIO system can use their web-browsers to create and edit
"forms" that are immediately capable of collecting data via web-browsers.
These web-forms contain Question items that constrain the information that
can go on the form. Question items can be "blank", "pickone",
"pickmany", "text area", "image", "visual analog scale", "hip range of motion", etc.
Validation rules defined by regular expression strings can be used to constrain
text input (action="template"). Interactive elements such as visual analog scales
available for insertion into forms
Once a form is defined, it can be used to collect data. This is as simple as
selecting a patient, selecting a form, and filling out the form.
Forms can be exported as XML and can be uploaded to a metadata
repository such as the OIO Library and re-imported into another OIO Server
"Workflows" can be defined to automate the activation of forms. Branch_on_condition, send_email, and other workflow_actions provide high-level tools for
rapid modeling of medical and clinical research web-application development.
"Schedules" use "scheduled_workflow" response actions to support user-definable event types. Year, Month, Week, and day views are available.
Once data have been collected, online "Reports" can be generated. This
involves the creation of datasets that can combine data from arbitrary
forms. Once a dataset is created, it can be queried online via logical
operations (and, or, and not).
"Live Reports" that organize data into spreadsheet-like tables for statistical analysis and export are also available. [Jump to Summary with Screenshots describing Live Reports]
Datasets can also be exported as comma delimited or XML file
for off-line analysis in Microsoft Excel, SPSS, SAS, or other statistical software.