|
|
16 Member(s) Online
- Overview
- Presentations
- Con Activities
- Travel/Lodging/Food
- Help Out
- Past Cons
PyCon is a 100% Volunteer-run Conference Organized by Members of the Python Community.
Site/Questions etc ?
|
|
|
Details of Talk
Click Here to Respecify your Query
| #37: |
Beyond Scripting: Using Python to Create a Medical Information System with Graphical Template and Database Schema Design
|
| Presented: |
Sun Feb 26, 2006
|
1
|
02:10 pm-02:55 pm
|
| Author(s): |
Matthew Harriger / University of Nebraska Medical Center
|
| Items: |
audio-no
handouts-yes
released-unknown
video-no
|
ADMIN
|
| Abstract: |
Python is often described as a "scripting language". While python is an
excellent choice for simple scripting tasks, it is also ideal for developing
complex applications. The Department of Surgery at the University of Nebraska
Medical Center is creating a medical information system called intuaCare using
Python, wxPython and other open-source tools and libraries.
intuaCare and intuaDesign are wxPython-based applications that provide
point-of-care access to patient records. intuaDesign is a graphical
template/interface designer that gives users the ability to create their own
data entry screens via drag-and-drop and also generates the appropriate
database tables for the storage of data. The forms generated by intuaDesign
are then used by intuaCare to collect and display clincal data. The data
collected is stored in a local database on the device, and synchronized to a
master Oracle database when a network connection is available.
This presentation will cover our reasons for selecting Python and wxPython as
the platform for intuaCare, and some of the features we were able to implement
using Python that would have been more difficult in other languages. A brief
demonstration of intuaCare and intuaDesign will be included in the
presentation.
|
| Item(s): |
Release Form not on File
|
Note: Talk recordings have come from different donors, with different levels of quality.
A suffix has been added to the basename of each recording reflecting this. For eventual upload to
a repository like archive.org, a formal naming convention has been followed:
pycon-{date}-{track}-{timeslot}-{talkno}-{donor}.mp3
For those who might prefer a more human-meaningful name, the recordings have MP3/Ogg/Flac ID3
information within and a simple python script could rename your collection to something in a {title}-{author}
form.
|