|
Included Updates
None
Product Update Description
Avatar CWS 2022 is updated to Avatar CWS 2023
|
Topics
• NX
• Upgrade
|
|
Included Updates
None
Product Update Description
The error '[SYNTAX]GetTXPlanProblems+4^TXPlanAutosave' that may occur in the 'Problem List' form is resolved.
|
Topics
• Problem List
|
-
Progress Notes - Editing Appointments after Autosave
An issue has been resolved in 'Progress Notes' forms that may cause autosaved notes attached to appointments that have been edited since the autosave to be switched to an 'Independent' note upon form entry.
Included Updates
None
Product Update Description
An issue is resolved in 'Progress Notes' forms that may cause autosaved notes attached to edited appointments to be switched to 'Independent' notes on form entry.
|
Topics
• Progress Notes
• NX
• Scheduling Calendar
|
|
Included Updates
None
Product Update Description
The following changes are made: 1) The error "<UNDEFINED>GetDescUnits+15^CWSVitalSignReport ^CWSVitalSignXRef("fld",14160)" which may occur while viewing patient vital signs in the chart view is resolved. 2) The error "<UNDEFINED>PrintHTML+92^cwsCHARTHTMLCWSVitalsEntry ^CWSVitalSignXRef("id",14160)" which may occur while viewing patient vital signs in the chart view is resolved.
|
Topics
• Vitals Entry
• Chart View
• Vitals
• Progress Notes
• Medical Note
|
-
Progress Notes (Group and Individual)
A modification has been made to Progress Notes (Group and Individual) to ensure that the following error is not received upon submission of notes: '[SUBSCRIPT]AuthResult+36^HRADAuthCheck^PAYAUTH'.
Included Updates
None
Product Update Description
The hard error '[SUBSCRIPT]AuthResult+36^HRADAuthCheck^PAYAUTH' that may occur in the 'Progress Notes (Group and Individual)' form is resolved.
|
Topics
• Progress Notes
|
-
Treatment Plan - Status Code
The Treatment Plan registry setting "Status Default Code" has been removed and the functionality is now controlled by "Site Specific Section Modeling".
-
Treatment Plan - Transcriber ToDo
An issue has been resolved with Treatment Plans where The error "[SYNTAX]GetSavedValue+12^TXPlanAutosave" may occur when selecting a Treatment Plan transcriber to-do.
-
Progress Notes - Multiple Session Start and End Times
An issue has been resolved in progress notes when the registry setting 'Multiple Start and End Times to Document Sessions' is enabled there could be an issue with the service duration not matching start and end times.
Included Updates
2
Product Update Description
The following issues are resolved: 1) The error "[SYNTAX]GetSavedValue+12^TXPlanAutosave" that may occur when selecting a Treatment Plan transcriber to-do. 2) The Treatment Plan registry setting "Status Default Code" has been removed. This functionality is now controlled by 'Site Specific Section Modeling'. 3) An issue that may prevent notes from being filed as 'Final' in Progress Notes forms when the 'Multiple Start and End Times to Document Sessions' registry setting enabled, and the duration does not match the start and end times.
|
Topics
• Treatment Plan
• NX
• Progress Notes
• Registry Settings
• Progress Notes (Group And Individual)
|
-
Treatment Plan Interventions - 'Assigned Services' grid
The 'Amount' field within the 'Assigned Services' grid in the 'Treatment Plan' form is updated to display after the 'Duration' field in the Chart View and Document Routing.
Included Updates
None
Required Updates
Avatar CWS 2022 Update 113
Additional Requirements
For Avatar NX Clients: Avatar NX Release 2023.02.00 is required for full functionality.
For myAvatar Clients: RADplus Client Update 3328-003 or RADplus Client Update 2513-012 is required for full functionality.
Product Update Description
Field 'Amount' that is a part of the 'Assigned Services' input within a Treatment Plan Intervention is now displayed after field 'Duration' in both Chart View and Document Routing.
|
Topics
• Treatment Plan
• Document Routing
• Chart View
|
|
Included Updates
None
Product Update Description
The Cache error "[UNDEFINED]productHook+9^ResultsTablePro1 *Count", which can occur when using the 'Results Entry (Results Main)' form to delete results, is resolved.
|
Topics
• Results Entry
|
-
Progress Notes (Group and Individual) - Reject note workflow
An issue has been resolved in "Progress Notes (Group and Individual)" where an error message would occur when a note with document routing enabled is routed, rejected, and then accepted.
Included Updates
None
Product Update Description
An issue is resolved in 'Progress Notes (Group and Individual)' forms where the message 'The appointment this note addresses is no longer available.' is displayed when finalizing a previously rejected Routed Document.
|
Topics
• Progress Notes
• NX
|
-
Progress Notes (Group and Individual) - The 'Default Staff Associated with Current Login User' registry setting
The 'Progress Notes (Group and Individual)' form and copies are enhanced to take into account the registry setting 'Default Staff Associated With Current Login User' in the 'Group Default Notes' section.
-
Progress Notes (Group and Individual) - Group Default Notes
The 'Group Default Notes' section of the 'Progress Notes (Group and Individual)' form and its copies are enhanced to support adding multiple clients to group notes based on caseload or unit.
To make use of this functionality, the following fields can be added via the 'Site Specific Section Modeling' form:
-'Add to Group - Use Caseload or Unit for Selection'
-'Unit'
-'Select Clients'
-'Add Selected Clients to Group'.
-
Progress Notes (Group and Individual) - 'Note Type' field
Ensure both the individual and group sections of the 'Progress Notes (Group and Individual)' form have the same selections available in the 'Note Type' field and include only active dictionary values.
Included Updates
None
Product Update Description
The following changes are made: 1) The 'Progress Notes (Group and Individual)' form and copies are enhanced to take into account the registry setting 'Default Staff Associated With Current Login User' in the 'Group Default Notes' section. 2) The 'Group Default Notes' section of the 'Progress Notes (Group and Individual)' form and its copies are enhanced to support adding multiple clients to group notes based on caseload or unit. The following fields are now available to be added via the 'Site Specific Section Modeling' form: 'Add to Group - Use Caseload or Unit for Selection', 'Unit', 'Select Clients' and 'Add Selected Clients to Group'. 3) An issue where the 'Progress Notes (Group and Individual)' form and copies can have different selections available for the 'Note Type' field is resolved. 4) An issue where the 'Progress Notes (Group and Individual)' form and copies may display an inactive selection in the 'Note Type' field is resolved.
|
Topics
• Progress Notes
• Group Progress Notes
• Registry Settings
|
|
Included Updates
6
Product Update Description
The error 'BSA: Unit mismatch; m2 expected' that may occur upon filing a 'BSA' vital sign reading from the 'Mednote' application is resolved.
|
Topics
• Vitals
• Chart View
• Vitals Entry
• Progress Notes
• Medical Note
|
|
Included Updates
None
Product Update Description
The 'Current Medications' widget is enhanced to improve performance.
|
Topics
• NX
|
-
Task List - Task Associations by Order Type
The following changes are made:
1) The field 'Order Type' is added to the 'Task Associations' form.
2) The 'Task List' application is enhanced to support 'Order Type' associations.
Furthermore, an issue in the 'Task Associations' form is resolved to ensure the 'Task Associations' field is cleared out after filing.
Included Updates
3, 4, 5, 6, 10, 11, 13, 13.1, 14, 17, 18, 20, 22, 24, 26, 27, 28, 30, 31, 32, 35, 37, 38, 39, 40, 41, 44, 45, 46, 48, 49, 50, 53, 55, 57, 58, 59, 61, 64, 66, 68, 69, 70, 71, 73, 76, 80, 82, 83, 84, 86, 87, 90, 94, 96, 98, 100, 103, 105, 106, 107, 108, 109, 110, 113, 117, 118, 120
Product Update Description
The following changes are made: 1) The field 'Order Type' is added to the 'Task Associations' form. 2) An issue in the 'Task Associations' form where the field 'Task Associations' would continue to show associations after filing is resolved. 3) The 'Task List' application is enhanced to support 'Order Type' associations.
|
Topics
• NX
• Task List
|
-
Dictionary Update - 'Plan Type' dictionary
The 'FHIR Care Plan Category' extended dictionary is added under the 'Plan Type' dictionary in 'Dictionary Update'.
-
Treatment Plan - 'Current Status' field
The 'Current Status' field is added to the 'Treatment Plan' form and its copies. The 'SYSTEM.tx_plan', 'SYSTEM.cw_tx_client_plan' SQL tables and the web service are updated accordingly. Also, the 'Display Treatment Plans in Selection Leaf for The Selected 'Current Status Codes' field is added to the 'Set System Defaults' form. The 'SYSTEM.cw_system_defaults' SQL table is updated accordingly.
In addition, the 'Set Current Status To Active When Plan Is Finalized' and 'Set Current Status to Completed On Plan End Date' registry settings are added. These settings give the user the ability to determine if the 'Current Status' field will be auto-populated based on the registry setting value.
-
Treatment Plan - 'SYSTEM.tx_plan' SQL table
The 'care_plan_text' field is added to the 'SYSTEM.tx_plan' SQL table. This field will capture the data on file in the 'Strengths', 'Weaknesses', and 'Discharge Planning' fields in the 'Treatment Plan' form.
-
Dictionary Update - Goal 'Status' dictionary
The 'FHIR Goal Status' extended dictionary is added to the goal 'Status' dictionary in 'Dictionary Update'.
Included Updates
3, 4, 5, 6, 10, 11, 13, 13.1, 14, 17, 18, 20, 22, 24, 26, 27, 28, 30, 31, 32, 35, 37, 38, 39, 40, 41, 44, 45, 46, 48, 49, 50, 53, 55, 57, 58, 59, 61, 64, 66, 68, 69, 70, 71, 73, 76, 80, 82, 83, 84, 86, 87, 90, 94, 95, 96, 98, 100, 102, 103, 105, 106, 107, 108, 109, 110, 113, 117, 118, 120, 123
Product Update Description
The following changes are made: 1) The new field 'Current Status' is added to the 'Treatment Plan' form and its copies. The SQL tables 'SYSTEM.tx_plan', 'SYSTEM.cw_tx_client_plan', and Treatment Plan web service are updated accordingly. 2) The new registry settings 'Set Current Status To Active When Plan Is Finalized' and 'Set Current Status to Completed On Plan End Date' are added. 3) The new extended dictionary 'FHIR Care Plan Category' is added under the 'Plan Type' dictionary (CWS #52003). 4) The new extended dictionary 'FHIR Goal Status' is added under the 'Status' dictionary (CWS #54014). 5) The new column 'care_plan_text' is added to the 'SYSTEM.tx_plan' SQL table. 6) The new field 'Display Treatment Plans in Selection Leaf For The Selected 'Current Status' Codes' is added to the 'Set System Defaults' form. The SQL table 'SYSTEM.cw_system_defaults' is updated accordingly.
|
Topics
• Treatment Plan
• Dictionary
• Web Services
• Registry Settings
• Set System Defaults
• Query/Reporting
|
-
Task List - Stat and Unscheduled one-time-only pharmacy orders
An issue is resolved to ensure that STAT and other unscheduled one-time-only pharmacy orders are immediately removed from the Task List Console when applicable.
-
NX - Task List Enhancements
The following changes are made to the Task List Console:
1) Support for documenting laboratory collections directly from the console.
2) Support for documenting orders with the order type categories: "Diet" and "Diet - Oral" as well as supplements directly from the console.
3) Orders requiring education and acknowledgement will now be indicated as additional tasks in the console.
4) An issue where STAT and other unscheduled one-time-only pharmacy orders were not immediately removed from the Task List Console is resolved.
5) Follow-ups recorded in eMAR will now dynamically refresh the Task List Console.
6) The Task List Console and related forms can now be enabled via the registry setting "Enable Task List Console".
7) Read-only tasks displayed in the Task List Console that are to be addressed in the eMAR (such as pharmacy orders) now respect the Order Entry role/user permissions that allow for permission to view and/or to document administration events.
Included Updates
3, 4, 5, 6, 10, 11, 13, 13.1, 14, 17, 18, 20, 22, 24, 26, 27, 28, 30, 31, 32, 35, 37, 38, 39, 40, 41, 44, 45, 46, 48, 49, 50, 53, 55, 57, 58, 59, 61, 64, 66, 68, 69, 70, 71, 73, 76, 80, 82, 83, 84, 86, 87, 90, 94, 95, 96, 98, 100, 102, 103, 105, 106, 107, 108, 109, 110, 113, 117, 118, 120, 121, 123, 124
Product Update Description
The following changes are made to the Task List Console: 1) Support for documenting laboratory collections directly from the console. 2) Support for documenting orders with the order type categories: "Diet" and "Diet - Oral" as well as supplements directly from the console. 3) Orders requiring education and acknowledgement will now be indicated as additional tasks in the console. 4) An issue where STAT and other unscheduled one-time-only pharmacy orders were not immediately removed from the Task List Console is resolved. 5) Follow-ups recorded in eMAR will now dynamically refresh the Task List Console. 6) The Task List Console and related forms can now be enabled via the registry setting "Enable Task List Console". 7) Read-only tasks displayed in the Task List Console that are to be addressed in the eMAR (such as pharmacy orders) now respect the Order Entry role/user permissions that allow for permission to view and/or to document administration events.
|
Topics
• NX
• myAvatar/myAvatar NX
• Task List
|
-
User modeled form - Form submission
A modeled form, in which there is a column mapping and table aliasing for Diagnosis, will successfully submit.
Included Updates
3, 4, 5, 6, 10, 11, 13, 13.1, 14, 17, 18, 20, 22, 24, 26, 27, 28, 30, 31, 32, 35, 37, 38, 39, 40, 41, 44, 45, 46, 48, 49, 50, 53, 55, 57, 58, 59, 61, 64, 66, 68, 69, 70, 71, 73, 76, 80, 82, 83, 84, 86, 87, 90, 94, 95, 96, 98, 100, 102, 103, 105, 106, 107, 108, 109, 110, 113, 117, 118, 120, 123, 124
Product Update Description
An issue is resolved where submission of User Modeled forms using the ICD10 Diagnosis Table Alias is blocked with 'Status is missing for row #' for a row which didn't have data entered.
|
Topics
• Modeling
• Problem List
|
|
Included Updates
None
Product Update Description
Avatar CWS is enhanced to support the HL7 FHIR (Fast Healthcare Interoperability Resources) data standard, relating to ONC (Office of the National Coordinator for Health Information Technology) certification.
|
Topics
• OrderConnect
• NX
|
-
Site Specific Section Modeling - Product Custom Logic
The "Use As 'File as Claim Note Text'" Product Custom Logic description is updated to be "Use As 'File as Claim Note Text' in 2300-NTE-02 - Free Text (80)".
The "Use as 'File as Claim Note Text' in 837P-2300-NTE-02/HCFA-1500 FL 19 - Single Response Dictionary" Product Custom Logic selection is added.
Note: Avatar PM 2022 Update 153 is required for full use of this functionality.
Included Updates
None
Product Update Description
The following is included: 1) The "Use As 'File as Claim Note Text'" Product Custom Logic description is updated to be "Use As 'File as Claim Note Text' in 2300-NTE-02 - Free Text (80)". 2) The "Use as 'File as Claim Note Text' in 837P-2300-NTE-02/HCFA-1500 FL 19 - Single Response Dictionary" Product Custom Logic selection is added. Note: Avatar PM 2022 Update 153 is required for full use of this functionality.
|
Topics
• Print Bill
• Progress Notes
• 837 Professional
• NX
|
-
'Progress Notes (Group and Individual)' forms
Ensure the ability to access 'Progress Notes (Group and Individual)' forms.
-
The 'Clinical Notes Mapping' form
The 'Clinical Notes Mapping' form is added. This form gives a user the ability to map individual forms, progress notes, and note types to one of the CCDA Document types.
In addition, the 'SYSTEM.cw_clinical_notes_mapping' SQL table is added to capture the information filed in the 'Clinical Notes Mapping' form.
-
Progress Notes - 'Are you releasing to myHealthPointe or External providers' field
The 'Are you releasing to myHealthPointe or External providers?' field is added to progress note forms when a corresponding mapping is defined in the 'Clinical Notes Mapping' form. The 'SYSTEM.cw_patient_notes' SQL table and progress notes web service are updated accordingly.
In addition, the 'Default 'Are you releasing to myHealthPointe or External Providers'' registry setting is added. This gives the user the ability to specify the code that will be defaulted to in the 'Are you releasing to myHealthPointe or External providers?' field in Progress Note forms.
-
Results Entry - 'Received Date' and 'Received Time' fields
Ensure the 'Received Date' and 'Received Time' fields are saved when the 'Results Entry' form is submitted.
Included Updates
3, 4, 5, 6, 10, 11, 13, 13.1, 14, 17, 18, 20, 22, 24, 26, 27, 28, 30, 31, 32, 35, 37, 38, 39, 40, 41, 44, 45, 46, 48, 49, 50, 53, 54, 55, 57, 58, 59, 61, 64, 66, 68, 69, 70, 71, 73, 76, 80, 82, 83, 84, 86, 87, 90, 94, 95, 96, 98, 100, 102, 103, 105, 106, 107, 108, 109, 110, 113, 117, 118, 120, 121, 123, 124, 126, 127, 130
Required Updates
Avatar CWS 2022 Update 130
Product Update Description
The following changes are made: 1) The new form 'Clinical Notes Mapping' is added. 2) The new field 'Are you releasing to myHealthPointe or External providers?' is added to progress notes forms. The SQL table 'SYSTEM.cw_patient_notes' and progress notes web service are updated accordingly. 3) An issue is resolved where the 'Received Date' and 'Received Time' fields are not saved when the 'Results Entry' form is submitted. 4) The error '[NOROUTINE]setupServiceStatus+13^ProgressNotes1 *ServiceStatus' is resolved that occurs when opening 'Progress Notes (Group and Individual)' forms in Cal-PM systems.
|
Topics
• Progress Notes
• NX
• Clinical Notes Mapping
• Web Services
• Health And Review Of Systems
• Registry Settings
• Results
• Results Entry
|
|
Included Updates
3, 4, 5, 6, 10, 11, 13, 13.1, 14, 17, 18, 20, 22, 24, 26, 27, 28, 30, 31, 32, 35, 37, 38, 39, 40, 41, 44, 45, 46, 48, 49, 50, 53, 54, 55, 57, 58, 59, 61, 64, 66, 68, 69, 70, 71, 73, 76, 80, 82, 83, 84, 86, 87, 90, 94, 95, 96, 98, 100, 102, 103, 105, 106, 107, 108, 109, 110, 113, 117, 118, 120, 121, 123, 124, 126, 127, 130, 130.1
Product Update Description
Avatar CWS is enhanced to support other products and modules.
|
Topics
• Progress Notes
• Progress Note Corrections
• Scheduling Calendar
• Product Final to Draft Override
|
-
Progress Notes (Group and Individual) - Remove Client From Group
Ensure the ability to remove a client from a group in the 'Progress Notes (Group and Individual)' form.
-
Progress Notes (Group and Individual) - Group Default Notes
The 'Group Default Notes' section of the 'Progress Notes (Group and Individual)' form and its copies are enhanced to support adding multiple clients to group notes based on caseload or unit.
To make use of this functionality, the following fields can be added via the 'Site Specific Section Modeling' form:
-'Add to Group - Use Caseload or Unit for Selection'
-'Unit'
-'Select Clients'
-'Add Selected Clients to Group'
-
Progress Notes (Group and Individual) - The 'Default Staff Associated with Current Login User' registry setting
The 'Progress Notes (Group and Individual)' form and copies are enhanced to take into account the registry setting 'Default Staff Associated With Current Login User' in the 'Group Default Notes' section.
-
Progress Notes (Group and Individual) - 'Note Type' field
Ensure both the individual and group sections of the 'Progress Notes (Group and Individual)' form have the same selections available in the 'Note Type' field and include only active dictionary values.
Included Updates
15
Required Updates
Avatar CWS 2023 Update 15
Product Update Description
The following changes are made: 1) The 'Progress Notes (Group and Individual)' form and copies are enhanced to take into account the registry setting 'Default Staff Associated With Current Login User' in the 'Group Default Notes' section. 2) The 'Group Default Notes' section of the 'Progress Notes (Group and Individual)' form and its copies are enhanced to support adding multiple clients to group notes based on caseload or unit. The following fields are now available to be added via the 'Site Specific Section Modeling' form: 'Add to Group - Use Caseload or Unit for Selection', 'Unit', 'Select Clients' and 'Add Selected Clients to Group'. 3) An issue where the 'Progress Notes (Group and Individual)' form and copies can have different selections available for the 'Note Type' field is resolved. 4) An issue where the 'Progress Notes (Group and Individual)' form and copies may display an inactive selection in the 'Note Type' field is resolved. 5) An issue where the 'Progress Notes (Group and Individual)' form and copies may result in an '[UNDEFINED]fld286+19^ProgressNotes2 *PT(291)' error after attempting to remove a client from a group is resolved.
|
Topics
• Progress Notes
• Group Progress Notes
• Registry Settings
|
| |