Syndicate

Recent Tweets

FreeMED

FreeMED is a direct descendent of AMOS, a Pascal/DBase program which was created in 1983 before the widespread use of relational databases and object oriented programming.

FreeMED is currently hosted by the FreeMED Software Foundation, with downloads hosted by Sourceforge.
It uses Subversion as a Concurrent versioning system, which it has used since it was migrated from CVS in 2005.

FreeMED is mainly written in PHP, and makes heavy use of SQL, favoring the MySQL database engine. It also uses some bash, Perl, and small pieces written in other languages. Its interface is primarily web-based, but web services interfaces, such as XML-RPC, are also available.

Modular Electronic Medical Record

FreeMED stores and represents its medical data as a group of "modules", which consist of a database model and a user interfaces. Each of the disparate modules are then virtually connected together by means of relational database table fields referencing other modules and basic patient demographics. This allows FreeMED to add and remove core database functionality by adding and removing modules without having to reprogram its interface.

External Billing System (REMITT)

FreeMED uses an external billing program called REMITT (REMITT Electronic Medical Record Information Translation and Transmission). The name "REMITT" is a Recursive acronym. It communicates with REMITT via an authenticated XML-RPC connection. This connection, once established, allows the transmission of medical billing data as a monolithic chunk of XML. This is then processed into a meta-format via XSLT, and finally processed into its final format and transmitted to its ultimate destination.
This methodology allows for multiple formats of output to be generated from the same base data.

Short Description:

An opensource electronic medical record and practice management system which has been developed since 1999.

Rewritten / redesigned REMITT billing service. For all those who hated the instability and pain behind some of the older REMITT versions, not to fear, the new version of REMITT is now a self-contained J2EE application. It also supports such niceties as eligibility verification, remote configuration management, foreign id support, SFTP push support, PGP/GPG encryption/decryption, and remittance callbacks with X12 835 parsing.The official REMITT site has more information on upcoming features here.

Database-backed data store. No longer do you have to rely on distributed filesystems and bizarre incantations to implement a distributed FreeMED setup ; it’s now as easy as setting up a load balancer. Scaling, ahoy!
Clinical Patient Order Entry (CPOE). Oft-requested, much desired feature, required by new meaningful use specifications.

Data normalization. Most of the system is now relying on normalized data fields against industry standard data sets, so your patient data is as portable as you’d like it to be.

Revamped reporting engine based on JasperReports. We’re using a standard reporting engine now, so designing your own reports is no longer a Byzantine task.
Scheduler improvements. It’s drag and drop, with block and group support, along with appointment templating and all of the modern scheduler trimmings.

Virtual “push” notifications. The user interface updates itself whenever the data updates itself, so you can be sure what you’re seeing is the latest version of the pertinent information, without having to resort to your “Refresh” button.
Semantic patient tagging. You loved it on Flickr, now gain the advantages of semantic tagging in finding patients.

Webcam patient image support. Grab a headshot of your patient for identification purposes with any web browser and a webcam, it’s as easy as that.
Full immunizations and vitals records. Industry standard data for vitals and immunizations, which can help facilitate machine reading and other integration efforts.

Drug sample tracking. Track drug sample lots in the event of a recall or other tracking purposes.

Access Control (ACL) rewrite. We’re getting serious about access control, so you won’t have to worry about overly loose access control. Give your staff and providers as little or as much access as they need.