Michael The drug problem you are worried about will only occur if the third party doesn't map the drugs correctly. By mapping the various fields correctly, is why a connversion from MD2 to BP worked so well - Frank did the mapping. I have succesfully imported a patient from MD3 (in XML) format into BP. MD3 also uses MIMS, and as mentioned BP uses APPCo. The drug mapping was done correctly and no problems encountered. If the 3rd party charges you for doing the conversion or sells you the conversion program, then they must ensure they do the mapping of the various fields correctly.
All my allergies came across from MD2. Some I had to slightly change - a good example is "Penicillin's" allergy had to be amended to "Penicillin" allergy. BP still displays all the allergies from MD2, so by looking at the Alleregy list, it is displayed. Some as mentioned just has to be slightly changed. Cedric -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael Christie Sent: Thursday, 19 July 2007 6:24 AM To: General Practice Computing Group Talk Subject: [GPCG_TALK] Migration to non MIMS database Dear All, May I beg your comments? We are considering moving from Locum to Best Practice. Apparently the third party database people tell me they can transfer all the data from Locum to BP, how well I don't know. One biggish problem is that Locum uses MIMS drug database which we are happy with, and BP uses APPCo. So as far as I know the migrating of the Pts drug history and current medication may mean just a document with a list of medications in the letters section of BP, not really putting the current medications into BP that can be straight away prescribed. Also current allergies which uses MIMS Interact, probably won't work on the new package as well as that drug database is different. If we used a package that had MIMS as a database my guess is that the Current Meds and allergies would come straight across to the new package. What comments do my colleagues have re the above? Rgds Michael Christie _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk _______________________________________________ Gpcg_talk mailing list [email protected] http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk
