Jan 01, 2013  Several years ago, Boston Medical Center’s Brian Jack, MD, and colleagues began looking at ways to help patients in the hospital care for themselves once they leave. With initial funding through a Partnerships in Implementing Patient Safety grant from the Agency for Healthcare Research and Quality (AHRQ), the Re-engineered Hospital Discharge (Project RED) intervention was born.

General InformationTechnologies must be operated and maintained in accordance with Federal and Department security andprivacy policies and guidelines. More information on the proper use of the TRM can be found on the.Website:Description:Project RED (Re-Engineered Discharge) provides evidence-based, Veterans Health Information Systems and Technology Architecture (VistA)-Integrated Discharge Instructions.

This software replaces a site`s existing Computerized Patient Record System (CPRS) discharge note with a patient-friendly discharge instruction booklet that is intended to improve the discharge process and decrease hospital readmissions. The RED intervention is founded on twelve discrete, mutually reinforcing actions intended to reduce re-hospitalizations and yield high rates of patient satisfaction.Project RED implements the `Louise` system which is comprised of a networked server with relational Microsoft Structured Query Language (SQL) Server database; a Graphical User Interface (GUI)-based data entry and management program (the `workstation`); a report generator that produces the After Hospital Care Plan (AHCP) booklet for patients to take home; and the bedside patient education system `Louise`.

The system works either in a completely stand-alone fashion, in which all patient data is entered via the workstation, or with any portion of the data populated from the hospital information technology systems.Technology/Standard Usage Requirements:Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations.

Automation Studio 6.0 free download latest version for windows. It is the full offline standalone setup of Automation Studio 6.0 for windows 32-bit and 64-bit operating system. This is an imposing engineering tool which is used to design circuit designs and simulation of electro-pneumatic and electro-hydraulic. Automation studio 6.0 download free. Education software downloads - Automation Studio Educational Edition by Famic Technologies and many more programs are available for instant and free download. Automation studio 6 full. Automation Studio 6.3 Crack + Keygen Full Updated Automation Studio Crack is a multi-user environment. This software allows you to perform club formative work on a project through data sharing and synchronization between different users. Download automation studio 6 64 bit for free. Business software downloads - Automation Studio by Famic Technologies Inc. And many more programs are available for instant and free download.

Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.Section 508 Information:This technology has not been assessed by the Section 508 Office. The Implementer of this technology has the responsibility to ensure the version deployed is 508-compliant. Section 508 compliance may be reviewed by the Section 508 Office and appropriate remedial action required if necessary. For additional information or assistance regarding Section 508, please contact the Section 508 Office at Section508@va.gov.Decision:Decision Source:TRM Mgmt GroupDecision Process:One-VA TRM v19.4Decision Date:Introduced By:TRM RequestVendor Name. Vendor Release InformationThe Vendor Release table provides the known releases for theTRM Technology, obtained from the vendor (or from the release source).VersionRelease DateVendor End of Life DateVendor Desupport Date4Current Decision Matrix Users must ensure their use of this technology/standard is consistent with VA policies and standards, including, but not limited to, VA Handbooks 6102 and 6500; VA Directives 6004, 6513, and 6517; and National Institute of Standards and Technology (NIST) standards, including Federal Information Processing Standards (FIPS). Users must ensure sensitive data is properly protected in compliance with all VA regulations. Prior to use of this technology, users should check with their supervisor, Information Security Officer (ISO), Facility Chief Information Officer (CIO), or local Office of Information and Technology (OI&T) representative to ensure that all actions are consistent with current VA policies and procedures prior to implementation.The VA Decision Matrix displays the current and future VA IT position regarding different releases of a TRM entry.

These decisions arebased upon the best information available as of the most current date. The consumer of this information has theresponsibility to consult the organizations responsible for the desktop, testing, and/or production environmentsto ensure that the target version of the technology will be supported. CY2019CY2020CY2021ReleaseQ1Q2Q3Q4Q1Q2Q3Q4Q1Q2Q3Q44Approved w/Constraints4, 5, 6Approved w/Constraints4, 5, 6Approved w/Constraints4, 5, 6Approved w/Constraints4, 5, 6Approved w/Constraints4, 5, 6Approved w/Constraints4, 5, 6Approved w/Constraints4, 5, 6Approved w/Constraints4, 5, 6Approved w/Constraints4, 5, 6Approved w/Constraints4, 5, 6Approved w/Constraints4, 5, 6Approved w/Constraints4, 5, 6Decision Constraints1Veterans Affairs (VA) users must ensure VA sensitive data is properly protected in compliance with all VA regulations.

All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with.2This technology should only be used when required by a Veterans Affairs (VA) business partner for an approved VA Project. Use of this technology must comply with ESCCB requirements which include: Signed Interconnection Agreements/Memorandum of Understanding agreements (MOU/ISA) with each external business partner, compliance with, and must implement appropriate requirements for all devices interacting with this technology. Anandmurti gurumaa yoga nidra. All instances of deployment using this technology should be reviewed by the local ISO (Information Security Officer) to ensure compliance with and standards and an ISO Risk Based Decision (RBD) must be approved by the local ISO/CIO before it can be used in the VA Production Environment. In cases where the technology is used for external connections, a full Enterprise Security Change Control Board (ESCCB) review is required in accordance,and. The local ISO can advise on the ESCCB review process and ensure are in place.3Per the May 5th, 2015 memorandum from the VA Chief Information Security Officer (CISO) FIPS 140-2 Validate Full Disk Encryption (FOE) for Data at Rest in Database Management Systems (DBMS) and in accordance with Federal requirements and VA policy, database management must use Federal Information Processing Standards (FIPS) 140-2 compliant encryption to protect the confidentiality and integrity of VA information at rest at the application level. If FIPS 140-2 encryption at the application level is not technically possible, FIPS 140-2 compliant full disk encryption (FOE) must be implemented on the hard drive where the DBMS resides.

Appropriate access enforcement and physical security control must also be implemented. Note: This list may not be complete. No component, listed or unlisted, may be used outside ofthe technology in which it is released. The usage decision for a component is found in the Decisionand Decision Constraints.NameDescription`Louise` is an animated conversational character that simulates face-to-face interaction between a patient and anurse.The `Louise` system is comprised of a networked server with relational database, a Graphical User Interface (GUI)-based data entry and management program (the `workstation`), a report generator that produces the After Hospital Care Plan (AHCP) booklet for patients to take home; and the bedside patient education system, Louise. The system works either in a completely stand-alone fashion, in which all patient data is entered via the workstation, or with any portion of the data populated from the hospital information technology systems.Project RED provides guidance to implement the Re-Engineered Discharge process for all patients, including those with limited English proficiency and from diverse cultural backgrounds. The toolkit includes a set of 12 actions hospitals can implement to ensure effective transition at discharge.