"Well, we could......"

Jogger is NOT a PM or EMR system, but it can be

Jogger was originally designed to handle intra-clinical communications, which was quite different from the traditional practice management (scheduling and billing) and electronic medical records (patient charts) systems.  Sandwalk did not plan to get into the PM and EMR market, which was already crowded with too many software vendors flagging many failed or ill conceived software architecture or information management strategies. Sandwalk needed a focus and niche market, and we found it in clinical operations.

 One day when talking with customers, we were surprised by a request: could Jogger Clinic interface with PM and EMR systems so that the physicians and nurses don't have to put up with the redundant and tedious data entry into their PM and EMR systems?  

PM and EMR systems share with the Jogger system one similarity: the purpose of recording and communicating information.  Therefore it is not difficult for Jogger to handle PM and EMR data as well.  What prompted our customers' request was their clear preference to Jogger's efficient, easy to use, and intuitive software interface.  Clinicians rarely need to type anything into Jogger, and only a few clicks of the mouse (or the touch sensitive screen) are all it takes to select an item.  Once they have used Jogger's efficient interface, typing into their old PM and EMR systems seemed like the stone age.  

The following is how Jogger can interface with other clinical systems:

Practice Management

PM systems hold patient demographics, insurance policies, scheduling templates and appointments, encounters (patient visits to clinics or hospitals), and itemized billing and payment information.  Jogger already holds encounter information.  Jogger can easily take in PM's appointments and demographics, and in return export to PM the itemized billing information, which is based on the treatment that was performed on each patient that the clinicians recorded in Jogger as they communicated to or coordinated with each other during a patient encounter.

It will not be very difficult for Jogger to handle insurance and payment information, although this will be a major addition to Jogger's capabilities since HIPAA has not fully standardized this aspect of the healthcare industry. 

Electronic Medical Records

EMR systems hold patient demographics, encounters (patient visits to clinics or hospitals), and patients' detailed medical conditions and treatment information.  Jogger already holds encounter and treatment information.  Jogger can easily take in EMR's demographics, and in return export to EMR the detailed treatment information.  

Physicians' largest complaint against EMR systems is the time it takes to enter data into their inefficient interfaces.  Most EMR system designers have done a poor job in optimizing the interface according to the needs of physicians, especially when no two physicians work in the same way.  Efficient and elegantly laid out interface is the hallmark of the Jogger system.  Sandwalk can customize and add to the basic elements of Jogger in order to simplify the data entry of EMR information.