Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

Merging CPS 10 databases

CPS, C-EMR, PM

Last Post by Anonymous 1 second ago

4 Posts

4 Users

0 Reactions

64 Views

RSS

mj2718

(@mj2718)

Posts: 54

Trusted Member

Topic starter

We are considering merging 2 existing CPS 10 databases into a single database. Has anyone out there done this already?

We are working with a consultant but not sure we understand all the potential issues that may occur.

We are planning to merge both clinical and practice management information.

Can anyone provide feedback on the experiences you've had?

Thanks -Matt Johnson | IS Analyst | Fisher-Titus Medical Center | [email protected]

Posted : October 28, 2013 5:22 am

justinbelcher

(@justinbelcher)

Posts: 130

Estimable Member

Sounds exciting. The obvious work will be in avoiding collision of primary keys. The primary keys in CPS tables are those numeric(19) values you see everywhere, and they are generated roughly to match the time they were created. You basically need to scan both databases and check to see [for each object type] if the same primary key was used in both DBs. If there is a collision, and there will likely be many, you will need to replace ALL references to that primary key in one of the databases. Unfortunately for you not all references are mapped using foreign key constraints so you'll need to consider every column in every table. This is an incredibly daunting task. I hope your consultant is good.

If you choose to develop a process like that, I encourage you to get the final process and program wrapped up in a neat package that can be used again. Let's hope that no more than one company in the community ever has to go through that. You can decide based on your morals and business needs whether to sell or open-source the package. Here's one vote for open source. Good luck.

Posted : December 11, 2013 12:17 pm

jdibiasio

(@jdibiasio)

Posts: 66

Trusted Member

We did this for 9.5 (same thing essentially). this is going to take a LOT of time and becomes very tedious.

your destination DB needs to line up perfectly with the one being merged. so forms, clinical kits, variables for drug/test administration. We also had patients visit both sites and had to merge a large number of charts.

Posted : December 15, 2013 11:43 pm

acantu

(@acantu)

Posts: 722

Prominent Member

You also want to make sure there is no SDIDs, PIDs, and other important key factors that link all OBS Terms, Documents, and Patient Information to Cross. A lot of work to validate, but if you are lucky, you wouldn't have to do this, but most like you might have to make some modifications to the keys and all supporting table records that use those keys to link.

Posted : January 15, 2014 2:17 am

Share:

24 Forums
9,940 Topics
39.9 K Posts
1 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed

Powered by wpForo Powered by wpForo version 2.4.0