clearhealth 0.1 (CHMobile For iPhone branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News clearhealth 0.1 (CHMobile For iPhone branch)
# 1  
Old 04-15-2008
clearhealth 0.1 (CHMobile For iPhone branch)

Image ClearHealth is a practice management system and EMR. It takes DNA from the FreeMED and OpenEMR projects, is based on the smarty templating engine, and uses the FreeB2 medical billing engine. It includes support for medications, SOAP data entry, clinical reporting, e-prescribing, and much more. It includes support for the iPhone and iPod touch. License: GNU Lesser General Public License (LGPL) Changes:
This release defaults to using the demo.clear-health.com site. This can be changed through the /Applications/CHMobile.app/Connection.plist file. The schedule tab now expects "simple_provider_report". The Labs module was enabled. Some known issues remain: selecting the Transcription or Pictures button crashes the application, and sections load slowly as each button completely reinitializes that section. The icons are currently hideous, too big, and strange.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. What is on Your Mind?

Nuclear Elephant iPhone Wipe making your iPhone Safer for Resale

For those with the iPhones here might read up how to wipe your personal data off the phone before reselling or trade-in. ;) source: Nuclear Elephant: iPhone Wipe June 1, 2008: Making your iPhone Safe for Resale Since my posts regarding the iPhone restore mode being insufficient for wiping... (0 Replies)
Discussion started by: sparcguy
0 Replies
Login or Register to Ask a Question
UTRACE_ATTACH_TASK(9)						  utrace core API					     UTRACE_ATTACH_TASK(9)

NAME
utrace_attach_task - attach new engine, or look up an attached engine SYNOPSIS
struct utrace_engine * utrace_attach_task(struct task_struct * target, int flags, const struct utrace_engine_ops * ops, void * data); ARGUMENTS
target thread to attach to flags flag bits combined with OR, see below ops callback table for new engine data engine private data pointer DESCRIPTION
The caller must ensure that the target thread does not get freed, i.e. hold a ref or be its parent. It is always safe to call this on current, or on the child pointer in a report_clone callback. For most other cases, it's easier to use utrace_attach_pid instead. UTRACE_ATTACH_CREATE Create a new engine. If UTRACE_ATTACH_CREATE is not specified, you only look up an existing engine already attached to the thread. UTRACE_ATTACH_EXCLUSIVE Attempting to attach a second (matching) engine fails with -EEXIST. UTRACE_ATTACH_MATCH_OPS Only consider engines matching ops. UTRACE_ATTACH_MATCH_DATA Only consider engines matching data. Calls with neither UTRACE_ATTACH_MATCH_OPS nor UTRACE_ATTACH_MATCH_DATA match the first among any engines attached to target. That means that UTRACE_ATTACH_EXCLUSIVE in such a call fails with -EEXIST if there are any engines on target at all. Kernel Hackers Manual 2.6. July 2010 UTRACE_ATTACH_TASK(9)