Search results

From OpenEMR Project Wiki
  • VISOLVE>> The data need to be secured when it is at "rest". This is to avoid the il VISOLVE>> Based on my understanding, i believe that the above techniques should wo
    1 KB (216 words) - 18:48, 9 September 2012
  • #* Visolve Selvi and team
    791 bytes (114 words) - 02:55, 9 September 2012
  • VISOLVE>> As per HIPAA Security rule, 'Unique User Identification' usually refers t VISOLVE: The idea you have proposed for "authorized user" (storing the workforce d
    3 KB (531 words) - 19:04, 9 September 2012
  • ...Bowen: This is a discussion that I had previously with Sena Palanasami of Visolve a few weeks ago. HIPAA requires that patients can review and correct ask t
    1 KB (207 words) - 18:19, 9 September 2012
  • === Basic Visolve Actions ===
    4 KB (639 words) - 18:39, 8 September 2012
  • VISOLVE>> The purpose of this feature is to make sure that the patient information
    1 KB (211 words) - 03:02, 9 September 2012
  • :Considered finalized by Visolve "Automatic log off comes under gap eligible criteria [Criteria categorized :‎[[File:ViSolve_Logo_Small.png|link=http://www.visolve.com/solutions-services/healthcare_services/meaningful-use-consulting-proces
    2 KB (210 words) - 10:00, 12 January 2014
  • Based on Visolve's Estimation document no new development needs to be done. However, we will
    4 KB (549 words) - 02:09, 26 February 2014
  • ...h at [[OpenEMR Professional Support#ViSolve|Visolve]]) ([http://github.com/visolve-openemr/openemr repository]) ...://github.com/visolve-selvi/openemr repository1]) ([http://github.com/devi-visolve/openemr repository2])
    18 KB (2,311 words) - 07:44, 9 January 2024
  • Completed by ViCarePlus Team, Visolve.
    2 KB (309 words) - 18:40, 8 September 2012
  • ...llowing reflects a discussion between Sam Bowen, MD and Sena Palanasami of Visolve.
    2 KB (345 words) - 22:20, 23 April 2012
  • VISOLVE>> Agreed and thanks for your views here.
    2 KB (309 words) - 02:50, 9 September 2012
  • date: 2010/04/16 11:12:52; author: visolve-selvi; state: Exp; date: 2010/04/07 06:45:42; author: visolve-selvi; state: Exp;
    91 KB (9,188 words) - 04:55, 22 December 2016
  • ===Analysis by ViSolve=== :The security team at ViSolve has been evaluating the SQL injection issue in OpenEMR. For this purpose th
    11 KB (1,561 words) - 06:41, 15 August 2020
  • :*Very nice information by [[OpenEMR_Professional_Support#ViSolve|Visolve]] that describes the MU2 criteria: ::*[http://www.visolve.com/uploads/resources/Meaningful%20Use%20Stage%202%20Final%20Rules.pdf 'Mea
    27 KB (3,626 words) - 10:12, 15 February 2017
  • Completed by ViCarePlus Team, Visolve.
    3 KB (418 words) - 02:45, 9 September 2012
  • Sena Palanasami - Visolve<br> Karthik - Visolve<br>
    14 KB (2,315 words) - 02:53, 9 September 2012
  • <TD ALIGN=LEFT>Visolve needs input re Data Integ from SF community</TD> <TD ALIGN=LEFT>Visolve nearing 100%</TD>
    32 KB (5,038 words) - 02:49, 9 September 2012
  • ...[[OpenEMR_Commercial_Help#MI2 | Medical Information Integration, LLC]] and Visolve
    3 KB (429 words) - 20:06, 1 April 2014
  • ===ViSolve=== :[http://www.visolve.com/ www.visolve.com]
    8 KB (1,014 words) - 13:53, 26 April 2023

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)