Difference between revisions of "PMT"
Becky.Matias (talk | contribs) |
|||
| Line 6: | Line 6: | ||
The Problem mapping tool enables organizations to convert patient problem lists and problem-based build content from the current Medcin ICD-9 to IMO (Intelligent Medical Objects) that contain both ICD-9 and ICD-10 codes. This tool is available Allscripts Enterprise EHR version 11.x and is a prerequisite to the installation of v11.4 or later versions. | The Problem mapping tool enables organizations to convert patient problem lists and problem-based build content from the current Medcin ICD-9 to IMO (Intelligent Medical Objects) that contain both ICD-9 and ICD-10 codes. This tool is available Allscripts Enterprise EHR version 11.x and is a prerequisite to the installation of v11.4 or later versions. | ||
| − | While IMO does include ICD-9 and ICD-10, this tool is meant to map Medcin ICD-9 terms to IMO ICD-9 terms, not to ICD-10. The mapping files created and defined in the PMT will be used to convert instance data within the Enterprise EHR. For this reason, it is only acceptable to map a term when the Medcin and IMO terms carry the same exact meaning. While the exact words and abbreviations may differ slightly, as long as the meaning is exactly the same it can be mapped. | + | While IMO does include ICD-9 and ICD-10, this tool is meant to map Medcin ICD-9 '''terms''' to IMO ICD-9 '''terms''', not to ICD-10. The mapping files created and defined in the PMT will be used to convert instance data within the Enterprise EHR. For this reason, it is only acceptable to map a term when the Medcin and IMO terms carry the same exact meaning. While the exact words and abbreviations may differ slightly, as long as the meaning is exactly the same it can be mapped. |
==Requirements== | ==Requirements== | ||
Revision as of 18:48, 23 September 2013
Problem Mapping Tool
Description
The Problem mapping tool enables organizations to convert patient problem lists and problem-based build content from the current Medcin ICD-9 to IMO (Intelligent Medical Objects) that contain both ICD-9 and ICD-10 codes. This tool is available Allscripts Enterprise EHR version 11.x and is a prerequisite to the installation of v11.4 or later versions.
While IMO does include ICD-9 and ICD-10, this tool is meant to map Medcin ICD-9 terms to IMO ICD-9 terms, not to ICD-10. The mapping files created and defined in the PMT will be used to convert instance data within the Enterprise EHR. For this reason, it is only acceptable to map a term when the Medcin and IMO terms carry the same exact meaning. While the exact words and abbreviations may differ slightly, as long as the meaning is exactly the same it can be mapped.
Requirements
- SQL Server 2000 or later
- Version 11.x
- Allscripts recommends that you are on the most recent Medcin release
- A connection to the production database server (or a copy of the production database server)
What Can be Mapped
Patient Instance Data
- Active Problems previously entered in actual patient charts
- Past Medical History Problems previoulsy entered on actual patients
- Family History Problems previoulsy entered on actual patients
- Social History Problems previoulsy entered on actual patients
Problem-Based Build (configuration) data
- Problems linked to CareGuide templates
- Problems linked to Flowsheets
- Problems linked to HPI Problem NoteForms
- Problems linked to Master (Specialty) Favorites Lists
- Problems linked to Personal (User) Favorites Lists
Charge Diagnosis-Based Build (configuration) data
- ICD-9s Linked to Diagnosis Group (Master) Favorites Lists
- ICD-9s Linked to Diagnosis User (Personal) Favorites Lists
- ICD-9s Linked to Exploding Sets
- ICD-9s Linked to Patient Past Diagnoses
- ICD-9s Linked to Subgroups (Diagnosis)
Before you Begin
It is important to understand the tool and the reasons for using this tool. In addition to reading through the documentation there are videos that are available in Client Connect that would be beneficial to watch. The links below will get you started.
Accessing the Tool
The first step is to download the tool and place it on your database server of your production environment (or a copy of that environment). Specific installation instructions are available on Client Connect.
Once the tool has been installed it is important to note that the PMT comes with new Security privileges that need to be assigned in order to access it.
The two new user Security Classifications available are:
- Problem Mapping Tool Access- This classification contains the Security Code of PMT Access which grants the user's assigned the ability to access the mapping tool.
- Problem Mapping Tool Admin - This classification contains the Security Codes of PMT Access listed above and PMT Administration which grants users the ability to perform administrative functions within the tool, such as run frequency programs, import an Allscripts mapping file, and configure problem search location.