In February of 2012, PCC will release Partner 6.5. Patient Checkin (
checkin) and the Patient Editor (
notjane) now include fields for race, ethnicity, language, and confidential communication preferences, 2012 RVU values are included in this update, and our development team has completed many other small feature requests and bug fixes.
Contact PCC Support at 1-800-722-1082 for information about these or any features in Partner.
Patient Preferred Languages
You can now enter and review a patient’s languages in Partner. The second step of Patient Checkin (
checkin) includes the new fields.
You can also enter the information in the Patient Editor (
notjane) or while adding a patient.
You can use the asterisk (*) to search the list quickly, and enter up to three languages.
Language information entered into Partner is available in PCC EHR, and vice-versa.
Migrate From Patient Status Flags?: Has your office been using patient status flags to indicate language preference? Now might be a good time to migrate your language records to the new discrete patient language fields. PCC Support can even help you automatically enter languages in patient records, based on their status flags, and then remove the flag for you. Contact PCC Support for assistance.
Why Track This Information?: Language information could help you contact patients in families using their primary language, or you could use the information to evaluate whether your office needs an interpreter. You can use languages as variables in form letters, and you can use Patient Recaller (
recaller) to find groups of patients with the same languages. Maintaining confidential contact preferences also helps your office meet one of the requirements for the ARRA incentive program.
Confidential Communication Preferences
You can now enter and review a patient’s confidential communication preference in Partner. The second step of
checkin includes the new fields.
You can also enter the information in
notjane or while adding a patient.
Checking off a particular communication preference reveals the fields for that preference. For example, if the patient has a private address distinct from their parents, you can select Mailing Address and enter that new address.
Your office can disable the communication preference fields if you do not wish to collect this information. Communication preferences entered into Partner are available in PCC EHR, and vice-versa.
Why Track This Information?: Confidential communication preferences are used to contact a patient about an issue before, or in addition to, their custodian or guarantor. This is useful for medical concerns that the patient themselves are responsible for maintaining or else are private. You can use communication preferences as variables in form letters. Maintaining confidential communication preferences also helps your office meet one of the requirements for the ARRA incentive program. Finally, PCC will introduce new automated contact tools later in 2012, so collecting contact information now may prove more useful soon.
Update Race and Ethnicity During Checkin
Partner 6.5 displays patient race and ethnicity on the new second step of Patient Checkin (
checkin), along with the other new fields. You can update that information when you check in the patient. Race and ethnicity were added to
notjane in a prior release.
Recording race and ethnicity for each patient helps your office meet one of the requirements for the ARRA incentive program. Race and ethnicity information entered into Partner is available in PCC EHR, and vice-versa.
2012 RVU Values
Your PCC reporting suite now includes the 2012 RVU data values. When you use PCC’s custom RVU reports and Dashboard, the new 2012 values are in place.
Minor Feature Improvements and Bug Fixes in 6.5
Partner now supports immunization dosages as small as .1mL. This feature was added to support the small doses used for PPD and FluMist, among others.
PCC EHR 6.5 includes 5010-compatibility updates for eligibility checking for Tennessee BCBS and Texas Medicaid.
In rare cases, a configuration problem could block the ability to merge patients with the
movekidprogram without indicating why. Now if this occurs, Partner tells the user about the configuration problem.
A leading “0” in front of the NDC dose amount could cause rejected claims. Partner now submits the NDC dose without a leading zero.
If you attempted to post payments with a claim ID for a claim that had been deleted, the Post Insurance Payments program (
pip) would sometimes fail without indicating why. Now if this happens,
pipindicates, “This claim has no undeleted charges.”
Sometimes, a Partner print file lock kept the nightly
daysheetfrom printing automatically. Partner now removes that lock nightly.