Misys Licenses Small Practice PM/EMR from iMedica

Well, in Amazing Charts, the database is protected so you can't even access the tables.

It should be protected. Can you imagine the chaos the would ensue if the typical end users could putz around in the main database. Tech support would go through the roof.

Anyway, I was referring to the ability to, "Extract," the data in those fields, into a Word Processor,  by knowing the exact name of the fields. In essence, a customized, "Mail Merge," of sorts. I wish all Vendors would allow this extraction/population into a Word Processor.

The ability to extract data from the main datatables is a nice feature.  Also, in iMedicaPRM you can set security rights in order to allow only certain users access to the main data tables (Administrator).  You can however pull data from the EHR if you have the security and build a custom report into Word.

Medtuity does not makes its tables inaccessible on SQL Server.  We've never had anyone muck up the tables.  We've scratched our heads several times in getting around security put in place by other vendors.  Unfortunately, that security is really a padlock on the door meant to provide only access by the vendor in hopes of preventing users from migrating to another product.  Otherwise, the vendor would always provide the password to the buyer/administrator.

We do take a preponderance of information (the clinical info) and scramble it before transport over the wire.  That feature can be turned off by the administrator.

mchasemd:

 Unfortunately, that security is really a padlock on the door meant to provide only access by the vendor in hopes of preventing users from migrating to another product. 

• protect the data from someone changing it when they shouldn't
• protect the user from an attorney who may accuse the user of having made changes if they could access the tables.
  
• prevent deletion/alteration of fields or tables that would cause a crash
  

If vendors only wanted to protect the data, they could make it read only.  In terms of providing audit trails ..... that is another matter.

DrMurdoch:

If vendors only wanted to protect the data, they could make it read only.  In terms of providing audit trails ..... that is another matter.

 

Not necessarily true in database management systems. 

• protect the data from someone changing it when they shouldn't
• protect the user from an attorney who may accuse the user of having made changes if they could access the tables
• prevent deletion/alteration of fields or tables that would cause a crash

The latter is just plain dumb, but there are endusers who will do that!

In terms of the ability to change data- electronic records should be held to the same standard of care legally as paper records. Even in the best of cases both can be altered by the unscrupulous, criminal mind. An attorney can accuse you of anything- but they have to prove their accusations in court, and if they are found to be overly aggressive in their accusations THEY can end up in trouble. Case in point: Michael Nifong who not only lost his license to practice law but recently went to jail for malicious prosecution of those white college kids, accusing them of raping a black prostitute!

URL: http://images.google.com/imgres?imgurl=http://www.dba-oracle.com/images/nifong_prison.jpg&imgrefurl=http://dba-oracle.blogspot.com/2007_01_07_archive.html&h=600&w=400&sz=66&hl=en&start=2&um=1&tbnid=LNFy7ZfkAXvLoM:&tbnh=135&tbnw=90&prev=/images%3Fq%3Dnifong%26svnum%3D10%26um%3D1%26hl%3Den%26rls%3Dcom.microsoft:en-US%26sa%3DN

The main problem with EMRs is that if you don't have the capability of locking down ALL the records except the one case in question, a good attorney can subpoena the complete EMR and have access to other records and use your overall manner of care with other patients as a weapon against you, s.a. "I see you didn't order a CT scan in 20 other cases with abdominal pain!".

>>> Well, in Amazing Charts, the database it protected so you can't even access the tables.

There is no way you can lock the Jet 4 backend. You can make it LOOK locked, but all you have to do is to make a new container and import all the objects. An MDE, which is MS Access' method of making an executable-like software will only hide the underlying code.

alborg:

>>> Well, in Amazing Charts, the database it protected so you can't even access the tables.

There is no way you can lock the Jet 4 backend. You can make it LOOK locked, but all you have to do is to make a new container and import all the objects. An MDE, which is MS Access' method of making an executable-like software will only hide the underlying code.

See...Al isn't even a hacker & he knows what to do...all it takes is a little know how and... 

>>> Al isn't even a hacker

Actually, I am a hacker... I LOVE to break into systems. I've even broken into the computer system of one of my local hospitals (they would put their system "down" at 3am, I would come along and turn it on again). When Paradox for DOS came out, I figured out their password algorhythm. The more the challenge, the greater the return!

In my high school years I could break into locker room padlocks (take off the back and follow the tumblers). I never got locked out of my house (key or no key)...

alborg:

>>> Al isn't even a hacker

Actually, I am a hacker... I LOVE to break into systems. I've even broken into the computer system of one of my local hospitals (they would put their system "down" at 3am, I would come along and turn it on again). When Paradox for DOS came out, I figured out their password algorhythm. The more the challenge, the greater the return!

In my high school years I could break into locker room padlocks (take off the back and follow the tumblers). I never got locked out of my house (key or no key)...

Thank God the practice of medicine has kept Al off the streets!

 What experience can you share on getting an interface between the imedica EMR and your practice management system (you did not say which one you are using)?

PamWaymack:

 What experience can you share on getting an interface between the imedica EMR and your practice management system (you did not say which one you are using)?

 Pam,

Keep in mind that iMedica started as a stand alone EHR prior to it's own PM being developed.   A one way outbound HL7 interface from the PM should not be a big deal.

Just ask the vendor (iMedica) what PMs they have interfaced from and what their specs are if they have not already created one from your PM.   I am not sure I understand where the mystery here lies.

Hi, I'm new to this board.

If you are looking for any information on real-life experiences with iMedica PRM, feel free to contact me.

I am the IT manager for a primary care group running PRM.  We have a two-way interface with our PM system, and with two major labs.  We have been using PRM since the 2005 beta version, and have been running the latest betas as they come out.  I have quite a bit of technical knowledge regarding the inner-workings of the system.

I know your question was not directed at me, but I thought I'd throw my experiences out there.  The interface with our PM system works almost flawlessly.  Every ongoing problem we have had with it, is due to sloppy data handling by our PM vendor.  Examples: No SS# sent as "--" instead of null or "", phone numbers sent as "0" instead of "" or null.  iMedica has done the best they can with handling things like this, and has even written some custom routines for us, because we got nowhere with trying to get the PM vendor to fix it.