OIO-1.0.0: Highly Customizable Forms, Schedules, Workflows, Reports, + PostgreSQL/Oracle-compatibility
Quick Start
- Free Download (under terms of GPL)
- Installation How-To (via Knoppix / Debian)
- Mailing List
- Project website
Introduction to OIO-1.0.0
- Andrew P. Ho, M.D. Assistant Clinical Professor, Department of Psychiatry, Harbor-UCLA Medical Center, University of California, Los Angeles
- Contact: [email protected]
Open Infrastructure for Outcomes (OIO) is a flexible data management system that supports user-definable metadata such as forms, reports, schedules, and workflows. It is implemented using Zope + PostgreSQL or Oracle database management system [ see architecture]. OIO is primarily used to support medical and clinical research applications. However, it has also been successfully used in eCommerce (e.g. OptoLight.Com).
Forms
Users can quickly design and modify forms via OIO's 100% browser-accessible tools. These forms ( schema) can be exported/imported as XML documents for re-use and interoperation with other systems. By creating and using the appropriate set of forms to model any medical, research, and business information, users can quickly tailor OIO-based applications to suit their unique and changing needs. We have been successful in training nurses, social workers, psychologist, college students, and physcians without programming background to create OIO forms. Forms contain Question Items which uses Responses (Itemtypes). Responses function as user-definable data types which can be re-used across Question Items. Arbitrarily complex Responses are modeled through OIO's growing list of Form Actions. |
|
|
|
Form ActionsForm Actions serve to
New Form Actions introduced in OIO-1.0.0 are:
|
|
Data Dictionary
|
|
SchedulesThis is a new module that supports user-definable EventTypes. This makes it easy to use custom-designed event-description forms (=EventType metadata) to define events and view multiple event-types (e.g. see all conferences and patient appointments) on the same schedule.
OIO-1.0.0's scheduling module uses the Calendar Tag product by Ty Sarna, Endicor Technologies. Thanks Ty! |
|
|
|
Event Notification via "Workflows"Since each Event is linked to a "scheduled_workflow" Form-Action, any workflow can be schedule for enactment at the event time. This means a workflow that contains a send_email activity can send an email notification, for example. |
|
WorkflowsThis is a new module that supports user-definable Workflows. A Workflow consists of a sequence of "Activity Steps" that are enacted by OIO when the workflow is invoked. There are currently 3 ways for a workflow to be invoked:
|
|
|
|
ReportsThis is an improved module that supports user-definable Reports. A Report allows data analysis of a merged dataset. A merged dataset is a user-defined subset of all forms-data. Data collected via forms are extracted, transformed, and loaded into a data mining table. A browser interface allows drilldown analysis of the merged dataset. New for OIO-1.0.0 :
|
|
|
|
|
|
|
|
Request for Comment
OIO-1.0.0 brings us closer to a tool that helps physicians, researchers, and others collaboratively model, modify, and construct informations systems that are specialized and yet easily portable.
However, much work remain. For example:
- XML import/export of schedules and workflows
- conditional Question item skipping inside a form
- automatic completion of forms from workflow step
- integration of Reports module with R (wwww.r-project.org)
- generic form layout metadata (support existing + XY layout)
If you find this work interesting or care enough to share your criticism or comments with us, please send email to our mailing list or to [email protected]. Most importantly, we hope you will download and use the software.
Acknowledgement
Dennis Halladay (Somalogic) - Oracle compatibility, data dictionary, quick reports, ParsedXML migration, extensive code review Daniel Auerbach (Cornell U.) - action=scheduled_workflow, schedules module Andrew Golovin (Ural Scientific Institute of Traumatology and Orthopaedics) - author of the new OIO logo Alex Chelnokov (Ural Scientific Institute of Traumatology and Orthopaedics) - originator of the Local_Text multi-lingual module and action=image, which now made action=file possible Gary Kantor (Case-Western) - there would be no pink_interface without Gary's strong advocacy Nandalal Gunaratne (Sri Lanka Teaching Hospital, Colombo South) - originator of the schedules module and action=autonumber Steve Vitale (U of Penn) - advocated for action=file James Smith, Keh-Ming Lin (Harbor-UCLA) - advocacy for workflows module Monica Soto-Rios (Harbor-UCLA) - save default data between forms and patients and numerous user-interface suggestions Carlos Callegari (Harbor-UCLA) - improvement in patient records display