Graham's *FREE* Synapse EMR

Announcement:  Sept 2006:  The best available information on Synapse EMR is located at http://www.synapsedirect.com

Demo Synapse via the download tab at http://www.synapsedirect.com

 

---

Now that my portal is working largely to my satisfaction, I'm about to start coding an EMR with integrated portal. I'm not intending to compete with the vendors here, just provide a basic system with a bias to specialist use. It will be based upon my existing EMR which I have coded in visual dbase.

Most likely I'll use postgresql for the backend, and hopefully it will portable across Windows, Linux and OSX.

To make it more usable for the USA, and other countries, I need to know what fields I need in the basic patient demographics. I've heard about a social security number. Anything else peculiar to the states that I need to include?

---

EMR
Where to Download and instantly demo the latest version of the EMR:

http://www.compkarori.com/emr/   (old site, being phased out as of Sept 2006)

Features:
- build using Rebol
- fast, crossplatform backend.
- secure portal for patient communication.

---

an EMR with an integrated portal.

---

Now that is music to my ears.

Graham, I've have to check out your portal soon. I admitted 10 people yesterday to hospital and am on call all weekend coming up. With 13 in the house already, I might not leave the hospital for a couple weeks.

Here's my first mock up of the GUI - 559 kbs.

http://www.compkarori.com/emr/remr.exe

I expect the final binary will be about 1Mb or less.
So, you should be able to carry your EMR around with you on usb disk!

"with a bias to specialist use."

What a horrible idea.
Just kidding.

What might you leave out/include to fufill this bias ?

The only real difference is that a specialist will have a referrer field, and letters generated from the consulation notes will be addressed to that referrer. But I guess if you're a family practioner, you can use the referrer fields to send a letter to the specialist. So, after all that, very little difference

what are you going to do for document management ?
Any thoughts on a tickler ? intraoffice messaging ? producing a referral letter .... etc.

document management

I presume you mean paper correspondence, results. Scan and store as pdf either as blobs in the database, or use the native filing system to store them. Probably have to add some searchable metadata.

tickler

What's that?

Intraoffice messaging

Not that difficult to embed inside the product. I've already written several standalone chat programs.

Producing Referral Letters

Either advise the other person to come in via the portal to examine the patient's notes ( you should see some of the referral letters I get - a paper dump of the recent patient notes, and a quick "Please see as per attached" ), or some way to automatically pull out the most important information with a quick note.

Graham:

If you provide me with your e-mail address, I'll send you our demographic sheet.

I can't wait to watch this project progress. I wish I would have taken computer programming courses in college instead of all those biochem classes I thought would help get me in medical school.

e-MDs several years ago was supposed to have a module they called "physician briefcase", whereby the chart could be pulled and taken on rounds. I don't know if that's still in the works but would be an awesome module. Medinotes offers this feature and the database synchronizes upon return to the office. I'm not currently using this module but would like to hear from those that do.

Email is drgchiu at compkarori.co.nz

I've uploaded a new mockup that shows how office chat might be incorporated. There's a little chat window at the bottom of the screen that is always visible no matter which tab you're in. The "chat" button toggles the visibility of the chat.

As it's a mock up, it will crash or look funny on resizing/typing.

I don't think you really need a physician briefcase. If you run a wireless connection back to base (GPRS, G3 or whatever), you can access the whole EMR. That's my intention anyway.

However, using embedded Firebirdsql, I can imagine pulling off all the patient's data, storing it on flash drive and taking it with you. Not too difficult methinks - just a little tedious coding.

gchiu, I think the interface mockup is outstanding. Was wondering what did you use to code it? I havent seen many applications that do not use the system scheme and still manage to look that sleek.

Congratulations and keep it up.

Using Rebol/View http://www.rebol.com/

I've just received ktdodson's demographic sheet. There's a lot more information there that needs to be captured, and I guess I'm going to have to rework the details tab into a mutli-tabbed panel as well to fit it all in.

A tickler is really a "Reminder System".

It can be called a Tickler Reminder System.

The Tickler is a system is used to remind staff to call or book a patient for a ‘repeat procedure’ or something that needs to be done on a regular repeating basis.

It should be easy to code.

Where the Reminders go when they expire is important.

OSCAR has some documentation on ticklers for their emr here ---> http://64.233.167.104/search?q=cache:oaYpIXITAHMJ:67.69.12.117:8080/oscarResource/Support/appt%2520screen%2520tabs+tickler+reminder&hl=en (on Page 7, use Control + F to find "tickler" quickly.)

I guess this is a to-do list such as:

immunisations
mammograms
DEXA scans

Items can be in a various states such as

not needed yet
ordered, not done yet
ordered, and no results back yet

I'll have to think more on how the workflow goes.