Sponsored Content
Special Forums News, Links, Events and Announcements Software Releases - RSS News clearhealth 0.1 (CHMobile For iPhone branch) Post 302185688 by Linux Bot on Tuesday 15th of April 2008 02:00:04 PM
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...
 

We Also Found This Discussion For You

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
Dancer::Engine(3pm)					User Contributed Perl Documentation				       Dancer::Engine(3pm)

NAME
Dancer::Engine - base class for Dancer engines SYNOPSIS
my $engine = Dancer::Engine->build( Serializer => 'JSON', $configuration ); DESCRIPTION
Dancer has various engines such Serializer engines, Template engines, Logger engines and Session handlers engines. This is the base class for all Dancer engines. If you're writing an engine of a common type (such as those mentioned above), you probably want to simply use their base class, which in turn use Dancer::Engine. For example, Template engines inherit from Dancer::Template::Abstract and Serializer engines inherit from Dancer::Serializer::Abstract. Those Abstract base classes inherit from Dancer::Engine. If a new type of Dancer engine is created, it is best it inherits from this class. ATTRIBUTES
name The name of the engine, such as JSON, or Simple. type The type of the engine, such as Serializer, or Session. METHODS
/SUBROUTINES config Fetches the configuration of the engine. my $configuration = $engine->config; You can only set the configuration at initialization time, not after. build Builds and returns the engine. my $engine = Dancer::Engine->build( $type => $name, $config ); AUTHOR
Alexis Sukrieh LICENSE AND COPYRIGHT
Copyright 2009-2010 Alexis Sukrieh. This program is free software; you can redistribute it and/or modify it under the terms of either: the GNU General Public License as published by the Free Software Foundation; or the Artistic License. See http://dev.perl.org/licenses/ for more information. perl v5.14.2 2011-11-30 Dancer::Engine(3pm)
All times are GMT -4. The time now is 02:09 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy