- DATE:
- AUTHOR:
- The SaiSystems team
PacEHR January 19th Release
PacEHR Release for January 19th
Reminder: PacEHR will be offline for 3 hours on Sunday the 19th from 3am to 6am eastern
Enhancements
1. ACO Quality Measure Report:
Pagination and Search: Enhanced navigation with pagination and search capabilities for larger datasets, ensuring a smoother user experience.
Percentage Display for Points: Adjusted point values to display as percentages, offering a clearer and more standardized view for the ACO Measures.
Data Export Enhancements:
New Columns: Added PacEHR Patient ID, ECM Patient ID, and Location Name
Additional Data: Includes all answers now
2. MIPS Quality Report:
Improved the accuracy of MIPS reporting by identifying and removing duplicate entries from record counts, ensuring precise performance evaluation.
3. Updated Facility Details from PointClickCare:
Enabled automatic syncing of facility details from PointClickCare into the Facility tables in PacEHR. This ensures that any changes made in PointClickCare are reflected seamlessly in PacEHR. This includes the timezone the facility for encounter note timing issues.
4. Updated Patient Screen with RAF Scores:
Added a display for Risk Adjustment Factor (RAF) scores directly on the patient screen. This enhancement allows providers to quickly assess a patient’s health risk, aiding in more informed clinical decision-making. See Below
5. AI Dashboard Enhancements:
Added new columns, “My Last Visit” and “POS” (Place of Service), to the AI Dashboard. These additions provide a snapshot of the last visit date and location, enabling providers to prioritize care more effectively.
6. Patient List (Export Function):
Included a new column, PacEHR ID, in the Excel export for patient lists. This ensures that patient records are easily traceable and linked within the system.
7. Inactive Reason Mandatory in Patient Demographics:
To ensure complete documentation, the “Inactive Reason” field is now mandatory when marking a patient as inactive. This helps maintain data integrity and traceability in patient records.
Bug Fixes
1. Facility MRN Alphanumeric Support:
Resolved an issue where the Facility MRN field in patient demographics only accepted numeric characters. It now supports alphanumeric values for better compatibility with varied facility codes.
2. Fixed Diagnosis Code availability on Encounter Screen:
Fixed an issue where previous assessments related to diagnosis codes assessment text were not displayed, ensuring that historical data is accessible for review.
3. Banner Hiding on Key Input:
Addressed a bug where using keyboard keys inadvertently caused the main banner to disappear. The banner now remains visible during data entry.
4. Fixed Facility Progress Notes showing ASCII Characters:
Corrected a formatting issue where encounter notes sent to PointClickCare (PCC) contained unnecessary question marks ‘?’, ensuring cleaner documentation.
5. Fixed Dashboard Refresh Issue:
Fixed a problem where the Open Notes list was getting refreshed automatically, this fix ensures that the previously selected information remains to be the same without refreshing the open notes screen.
6. Removed Incorrect G-Codes for PQRS Measure #236:
Resolved an issue where incorrect G-codes were displayed for PQRS Measure #236, ensuring compliance with reporting requirements.
7. AI Rounding Notes Update:
Ensured that rounding notes are accurately updated immediately after saving, avoiding discrepancies in note data.
8. Show dropdown/checkbox data in encounter history:
Resolved an issue where dropdown and checkbox selections were not displayed in the encounter history, ensuring that all user inputs are properly recorded and visible.
9. AI Dashboard: Default facility for new users:
Fixed a bug where the default facility was not displayed for newly created users on the AI Dashboard, ensuring accurate facility assignment upon user creation. not displayed
RAF Scoring Explanation
A RAF (Risk Adjustment Factor) score is calculated by taking into account a patient's demographic information like age, sex, and residence location, combined with their diagnosed medical conditions (ICD Codes) categorized into Hierarchical Condition Categories (HCCs), essentially assigning a numerical value to their overall health risk, with higher scores indicating a greater need for healthcare services and potential cost; this calculation is primarily based on ICD-10 codes documented in a patient's medical record, with each HCC assigned a specific weight that contributes to the final RAF score.
Key points about RAF score calculation:
HCCs:
The core component of RAF calculation is grouping diagnoses into HCCs, which represent clinically similar conditions with similar cost implications; the more severe HCCs a patient has, the higher their RAF score will be.
For instance, ICD Code E11.9 is in Category 19 and has a relative value of 0.175.
Demographic factors:
Age, sex, and residence status (like living in a nursing facility) also contribute to the RAF score.
Coding accuracy:
Accurate coding of patient diagnoses is crucial for generating an accurate RAF score, as it directly impacts the assigned HCCs and therefore the calculated risk. Only ICD codes submitting on a claim in the calendar year count toward the HCC Value. If E11.9 is not on any claim in 2025, this HCC Category might not be present and the patient would be a lower number.
Interpretation:
Nationally, a RAF value of 1.0 is considered average. Nursing Home patients are frequently between 2.0 and 3.0. The higher the value, the higher risk the patient represents.
PacEHR:
PacEHR Shows two values;
Current RAF score, which is the above formulas for demographics and ICD codes included on claims during this calendar year. (Encounters with a Date of Service this year)
MAX RAF Potential Score, which is the above formulas accounting for ALL ICD Codes on the patient problem list, regardless of being on a claim in the current year.
Example: