MEDITECH Practice Newsletter
Volume 1 Issue 1, Page 1
Making the Best MEDITECH Data Decision
By Mike Manolagas
As healthcare organizations round out their MEDITECH implementations, the Data Repository is now often included as one of the products that go live earlier than in years past.
If you are new to any system, you are more likely to have an immediate need to fulfill reporting and other data extraction requirements. Chances are you have already employ widespread in-house knowledge of and proficiency with Microsoft’s Office© products. Therefore, the recipients of the data you provide will come to expect the data you extract to be in a format, such as Excel, which is familiar to the end user.
If you have installed the core MEDITECH products and Data Repository, it would seem that the quickest and easiest way to get the data you need, would be from the Data Repository, because most of the relational database reporting tools that your staff already knows well can be used to get at your new MEDITECH data.
Although this may appear to be a simple decision, the reality is that it could back-fire and cause other unforeseen issues. This is due to the fact that there are times when it makes sense to use the Data Repository and there are times when it really does not make sense.
Without a great deal of experience with your new MEDITECH system, it can be difficult to know when to look towards the core transaction system database rather than the Data Repository. The following are some of the factors that have to be taken into consideration:
- Data in your transaction system is stored in a hierarchical database, which can only be accessed by the end user with the NPR Report Writer. If you do not have the in-house knowledge and skill-sets to use the NPR Report Writer the inclination will be to go to the Data Repository.
- The Data Repository is a real-time “dump” of most of your MEDITECH data into a normalized, relational database format. MEDITECH is committed to eventually getting all of the core systems data into the Data Repository. In the Client Server product line, there are over 300 enhancements between release 5.4 and 5.6, which either add new tables to Data Repository or add new information to existing tables. It is also possible to import or modify data in the Data Repository. This practice can create much confusion over time, especially if you are attempting to reconcile the Data Repository to your core systems.
- The core systems contain data that is complete and fully validated by the integrity checks that are inherent to the application software. It is by far the most reliable source to go to for data needs. However, without the appropriate NPR skill-set necessary to get at this data, it can be a daunting task, especially when faced with the pressure to deliver data to various departments immediately.
Despite the pressure to deliver data to those in your organization who need it, it is prudent to have a plan in place that will ensure that you go to the right source to get what you need.
In just about all cases, the following order of precedence will provide you with the most reliable data.
- If you can use the standard reports inherent to the software, they are your best option. You can be confident that they are carefully written by MEDITECH development staff that knows the data structures and all of their nuances extremely well. Using the standard reports will also ensure that as you update and move forward with new releases, your reports will remain in good working order. They may even be expanded to add more information and flexibility.
- If the standard reports do not provide you with the information you need, then you should consider what type of information you are trying to get at. If it is data that is going to be used to tie-out operational activity or to supplement any accounting functions, the core systems’ data should be used.
- If you want to fulfill a reporting need that encompasses a large data population and is geared more towards decision support or trending, then the Data Repository would be better suited. Its relational data structure is optimal for this purpose.
Implementing a plan that will enforce this line of decision making will save your organization time in the long run. It may take more time to implement at first. However, investing the time up-front to get it right will help ensure that everyone is receiving the most reliable data. This will fuel confidence and acceptance of the new system throughout the organization and make your role much easier.
If you are implementing or optimizing any MEDITECH solutions, we would love to help. Please contact us at 610-444-1233 or visit our website www.getvitalized.com for more tips and tricks!