Data integration in MIPSpro allows for data entry from various file types and formats. It's ideal for uploading large amounts of patient and visit data in single or multiple accounts.
Using data integration requires data in a format that the system can read.
Data integration types
Healthmonix uses 3 types of data integration:
1. Standard manual spreadsheet upload
Standard spreadsheets can include the file types listed below:
- Basic file types
- Excel spreadsheets (.csv, .xls, and .xlsx only. We can't accept .xlsm files.)
- .txt files
- Advanced file types
- QRDA I
- CCDs
2. SFTP
SFTP stands for Secure File Transfer Protocol. It's a network protocol that provides a secure way to transfer files between computers or servers.
SFTP allows you to set up automatic file exports from your EHR. These files can be uploaded nightly, weekly, or monthly.
3. API integration
This is a method where a client system retrieves data from a remote server or service using an Application Programming Interface (API). The client system pulls or fetches data from the API endpoint.
Some EMRs allow for an API integration. Contact your Account Manager or the Sales team to find out more.
Data mapping in MIPSpro
Codes are mapped to MIPS quality measures based on CMS-defined rules. Our system automatically maps codes during upload to determine measure eligibility and performance.
Measures have specific code requirements that must be present from both the denominator and numerator portion of each measure. We can perform basic code mapping or advanced code mapping.
Required data for patient records
If your patient files are separate from your visit files, you must ensure that your patient IDs match across all files being uploaded.
For example, if John Smith has visits in a visit file being uploaded as well as a patient file for his demographics, his patient ID (JS00012) needs to match across all files being uploaded into MIPSpro. This is to ensure that the eligible instances displayed is accurate.
If there are different patient IDs for the same patient, MIPSpro will create separate patients/instances, thus inflating your total eligible instances. If there are different patient IDs for the same patient in your files, you need to have our patient matching feature turned on. Otherwise, patient demographic information must be in each of your visit files.
Patient matching can be added to your account for an additional fee. Please reach out to our Sales Team to inquire about fees and to have this added.
Combining data from multiple sources
We typically see users needing to add the patient matching feature when they're combining data from multiple sources. Confirming that patient IDs match across all data sources is one of the most important aspects of combining data.
Since data combination is different for each user, you will want to reach out to our Sales team during the initial purchasing process. They will have additional questions for you to ensure that you have everything you need to combine your data and report successfully in MIPSpro.
The minimum required information includes:
- Patient ID (preferably de-identified and globally unique)
- Patient date of birth
- Patient gender
Optional information can include:
- Race
- Ethnicity
- Insurance
- Visit NPI
Required data for visit records
For a visit to be considered complete, specific criteria is needed. Requirements vary by measure but generally include:
- Date of service
- At least 1 CPT encounter (E/M) code
- At least 1 CPT/HCPCS (procedure) code
- ICD-10 diagnosis codes
-
HCPCS/CPT II codes for numerator performance (Met/Excluded/Not Met)
Some measures require G/F codes or special Healthmonix PROcodes. PROcodes are Healthmonix custom codes to address specific measures.
Please review the specification document for each measure to account for all needed data elements.
Spreadsheet requirements
If sending a spreadsheet, please ensure that each visit for your patients is in its own row. This helps account for all dates of service and visits.
This article was updated Dec. 5, 2024.