Free hipaa software for linux

X12::Parser::Readme is a Perl module for understanding configuration (cf) files for X12::Parser.

X12 transactions
ASC X12 standards define commonly used EDI transactions. The standards define a structure/format for exchange of EDI data.

Each transaction type is called a "transaction set". The smallest data item in a transaction is called an "element". Groups of related elements form a data segment. A data element separator separates the elements within a segment. A segment starts with a element which is called the segment ID, and ends with a segment terminator.

Logical groups of segments are called loops. There are some segments, which are used only to identify the beginning of a loop, these are called as control segments. A logical set of loops together form a "transaction set".

Similar transaction sets can be lumped together by enclosing them in data segments that are known as functional group headers and trailers. Functional groups are grouped together using interchange control headers and trailers.

Parsing
Unlike XML/HTML parsers which relies on "" tags to determine start and end of data blocks, X12 transactions rely on pre-defined values (segment IDs) to indicate start and end of related data blocks (loops). Developing a parser that would work for all X12 transactions poses a challenge in this respect, as each transaction has its own hierarchy of loops and start/end indicators.

This lead to the development of the X12 configuration file (cf) specification. The cf specification is created to specify details regarding the blocks/loops and start/end information in a common format. Cf files can be created for the different transaction sets. (see section Building a cf file).
Now you can parse your EDI data file by invoking the X12::Parser specifying the cf file to use. This allows you to parse any X12 transaction data files just by building the cf file for that transaction type.

Cf file specification for X12::Parser
The cf file specifies any transaction in a hierarchical form. It identifies the loops and segments in a transaction. This information is used to parse the transaction file. The X12::Parser uses the X12::Parser::Cf module to read the cf file information before parsing a transaction file. Since the X12::Parser parses files based on the cf file it allows the user to parse different X12 transaction types just by using the appropriate cf file. The user can use the cf files that are bundled with this package or create new cf files. The cf provided with this package is for the HIPAA X12 Ver 4010 X12 transactions.

A cf file has two types of information: section and key=value pairs. A section contains information in key=value pairs.

Freemed-YiRC is based on Freemed, but for Youth in Residential Care centers (YiRC).
Freemed-YiRC project runs on a web server, and the client can be ANY computer running a decent web browser with good table support.
FMYiRC is web-based!
- It is loaded on a Linux server at your agency.
- Your data is stored on your server at your agency.
- You own your data.
- All that is required to access FMYiRC is a computer with Internet access and a web browser
- Clients/workstations can use Windows, Linux, MacOS, etc...
- The Mozilla Firefox web browser is highly recommended
- With additional networking setup by your agency, one FMYiRC server can be used by many multiple off-site locations and mobile users.
FMYiRC was designed with security in mind
- Anyone in child care circles will tell you that all types of security are important when it comes to information relating to youth.
- For one, much consideration has to be paid to the HIPAA privacy rule!!!
- Access to FMYiRC can be restricted to the HTTPS protocol. This uses encryption (SSL) to ensure sensitive information is not intercepted by 3rd parties during transit across your network or the Internet.
- A properly configured FMYiRC Linux server will have its own firewall, in addition to the main Internet firewall at your agency.
- FMYiRC itself has a very fine-grade access control system. The administrator can control exactly what individual users have access to.
FMYiRC was designed to be reliable and fault-tolerant
- The entire design of FMYiRC was created by taking into account years of previous information system designs.
FMYiRC is easy to backup.
- There are only two major pieces to FMYiRC to backup:
- The database... very easy to backup with MySQL
- The FMYiRC software itself... contained in one place, very easy to backup using operating system utilities
- FMYiRC includes utilities to back itself up!
FMYiRC can make use of MySQL server real-time replication.
- You can set up two FMYiRC servers for a high level of fault-tolerance.
If one server goes down, users can switch over to the second server in very short order.
- Using a dual-server setup, downtime due to server maintenance or upgrades becomes next to nothing. You can switch your users to the secondary server, take the primary server down, perform the maintenance/upgrades without the pressure of a down server situation, bring it back up, switch the users back to the primary server, then do the same cycle with the secondary server if necessary.
FMYiRC is modular
- If you would like to add functionality to FMYiRC, you can do so by creating new software modules.
- Creating new modules for use with FMYiRC is relatively easy, documentation for this process is available.

Cottage Med is an Open Source Software that is ...
- Accessible & Affordable (Free, in fact)
- Easily Customizable and Expandable
- Designed by physicians for physicians
- Used by doctors in the U.S. and developing nations
- a template for FileMaker versions 5-7
Are you intimidated by computers? Is the cost of an electronic medical record ("EMR") beyond your reach? Are you a non-profit organization or a struggling doctor young or old? Our profession suffers with a blizzard of competing and conflicting EMRs. Bloated with unnecessary features, they cost a thiefs arm and a leg to boot. In Cottage Med you can quickly learn and easily reprogram our EMR just like visual Basic without programming experience.
Medicine has a big problem - no broadly accepted, affordable EMR standard exists. Cottage Med bridges your difficult present and unknown future by helping you step into a calmer, smoother, more productive now where you maintain full control over your information, full access to it, and the ability to smoothly export it to whatever future system or standards you choose. Open-Source EMRs are simply great solutions.
A flexible, ruggedly dependable and HIPAA-secure office system can be constructed with your old computer hardware for a few hundred dollars...with secure and wireless networking, PDA and multiple-office support, prescription writing and cross-platform compatibility built in. You should not believe the hype of the AAFP and hundreds of for-profit EMR software companies; our EMR solutions work right now, today, at no cost even without buying FileMaker.
Designed for PC, Apple and Linux environments, these templates run within the database program FileMaker (so its not a "pure" open-source project), but Cottage Med installs like childs play, develops quickly, and does the job to help improve healthcare. The templates designers offer free software support and system suggestions as needed.
Main features:
- point and click Apple/Windows interface for new users
- patient images, patient held records, pediatric growth charts
- practice statistics with powerful search functions for epidemiology and health maintenance studies
- open & industry standard database format
- wireless networking and PalmOS/PocketPC support
- links to other office programs including Microsoft Word, certificates, charts
- quick location of earliest appointment with iCal
- versatile printer and fax control
- multiple keyboard shortcuts for experienced users
- displays at 600x800, 780 x1024 and higher resolutions on demand
- easily copy and paste to replace any office stationery or forms with your own
- point and click note writing for rapid entry of examination
- custom medication lists, multiple user customizable templates
- patient registration, appointments, records & scripts
- supports an appointment timer, semi-automatic receipting of Medclaims