Difference between revisions of "Joint Legacy Viewer"

From Clinfowiki
Jump to: navigation, search
m (condensed history)
(Make references section)
Line 1: Line 1:
The Joint Legacy Viewer (JLV) is a browser-based graphical user interface used for viewing real-time medical information. It is capable of retrieving patient data from both the Veterans Affairs (VA) and Department of Defense (DoD) electronic medical record (EMR) systems and combining, normalizing, and displaying the information in customizable widgets. The system is mainly used by VA and DoD providers to help coordinate and facilitate care as Veterans transition between these departments. More recently, the viewer is offered to third-party providers as a means of sharing medical records of VA patients that are referred for care outside of the VA system.
+
The Joint Legacy Viewer (JLV) is a browser-based graphical user interface used for viewing real-time medical information. It is capable of retrieving patient data from both the Veterans Affairs (VA) and Department of Defense (DoD) electronic medical record (EMR) systems and combining, normalizing, and displaying the information in customizable widgets<ref name="FAQ" />,<ref name="TownHall">. The system is mainly used by VA and DoD providers to help coordinate and facilitate care as Veterans transition between these departments. More recently, the viewer is offered to third-party providers as a means of sharing medical records of VA patients that are referred for care outside of the VA system.
  
 
== History ==
 
== History ==
Line 6: Line 6:
 
The initial “Data Federation Release 0” of the JLV on December 31, 2013 was deployed to five VA Polytrauma Rehabilitation Centers as well as the Alaska VA Healthcare System. It used a new widget-based web platform that enabled display of seven different data domains and was able to provide access for up to 225 users. The next major revision, JLV version 2.2, was released in September 2014 and was made available to all VA Medical Centers on October 1, 2014. This update added support for eight additional data domains and included additional features such as “break the glass” functionality, improved performance and capacity, added support for up to 3,500 total users, and addressed various software bugs and security vulnerabilities.
 
The initial “Data Federation Release 0” of the JLV on December 31, 2013 was deployed to five VA Polytrauma Rehabilitation Centers as well as the Alaska VA Healthcare System. It used a new widget-based web platform that enabled display of seven different data domains and was able to provide access for up to 225 users. The next major revision, JLV version 2.2, was released in September 2014 and was made available to all VA Medical Centers on October 1, 2014. This update added support for eight additional data domains and included additional features such as “break the glass” functionality, improved performance and capacity, added support for up to 3,500 total users, and addressed various software bugs and security vulnerabilities.
  
JLV 2.4 was released July 2016. This update added usability enhancements and increased functionality of the widget interface as well as added a report builder function. Plans for future versions include adding the capability to view VA scanned documents and radiology images directly, blood bank integration, and audiometric data support. As of 8/2016, there were over 188,000 individual users with representation from every VA medical center in the country.  
+
JLV 2.4 was released July 2016. This update added usability enhancements and increased functionality of the widget interface as well as added a report builder function. Plans for future versions include adding the capability to view VA scanned documents and radiology images directly, blood bank integration, and audiometric data support. As of 8/2016, there were over 188,000 individual users with representation from every VA medical center in the country<ref name="TownHall">.  
  
 
== Features ==
 
== Features ==
Line 87: Line 87:
 
|}
 
|}
  
'''Context''': JLV is context-aware, meaning that the system is able to synchronize patient selection with other applications such as CPRS.  
+
'''Context''': JLV is context-aware, meaning that the system is able to synchronize patient selection with other applications such as CPRS<ref name="TownHall">.  
  
 
'''Patient Search''': If the patient context feature is not used, the JLV is capable of searching for patients by DoD ID, SSN, First/Last name, Date of Birth, Address, and Telephone. The system also maintains a list of recently viewed patients for convenience.
 
'''Patient Search''': If the patient context feature is not used, the JLV is capable of searching for patients by DoD ID, SSN, First/Last name, Date of Birth, Address, and Telephone. The system also maintains a list of recently viewed patients for convenience.
  
 
'''Report Builder''': Version 2.4 added the capability to combine multiple data elements into a report that can be saved as a single PDF file and exported or printed as needed.
 
'''Report Builder''': Version 2.4 added the capability to combine multiple data elements into a report that can be saved as a single PDF file and exported or printed as needed.
 +
 +
== References ==
 +
<references>
 +
<ref name="FAQ">Joint Legacy Viewer Frequently Asked Questions. Department of Veterans Affairs. October 2016. Retrieved 22 October 2016 from https://www.vapulse.net/docs/DOC-57124. </ref>
 +
<ref name="TownHall">Joint Legacy Viewer Town Hall- September 2016. Department of Veterans Affairs. 2 September 2016. Retrieved 22 October 2016 from https://www.vapulse.net/docs/DOC-52897</ref>
 +
</references>

Revision as of 23:28, 22 October 2016

The Joint Legacy Viewer (JLV) is a browser-based graphical user interface used for viewing real-time medical information. It is capable of retrieving patient data from both the Veterans Affairs (VA) and Department of Defense (DoD) electronic medical record (EMR) systems and combining, normalizing, and displaying the information in customizable widgets[1],Cite error: Closing </ref> missing for <ref> tag [2] </references>
Cite error: <ref> tags exist, but no <references/> tag was found