Re: CCHIT - sql

View: New views
3 Messages — Rating Filter:   Alert me  

Parent Message unknown Re: CCHIT - sql

by Jim Busser :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On 2009-11-07, at 6:51 AM, Sebastian Hilbert wrote:

I recommend to produce the sql for the test patients as described in the 
document and go from there.

The above might be best achieved by bootstrapping a fresh gnumed and running the remove patient script to remove individual test patients of which there are only about 15.

No-one has AFAICT diligently browsed clinical tables to determine how fully the remove script would purify *all* of the tables but I am figuring what we have now may be fully enough adequate.

The CCHIT patients and their test data and the test doctors and other personnel would need to be created / entered and at the point where the test data had been entered, the data dumped and saved. This would greatly facilitate re-testing at any point in the future.

Caveats:

1. We would need, stored with dumped data, the version of the gnumed database to which it related since any new gnumed may choke trying to directly import it... rather, anyone would bootstrap a fresh gnumed only up to the desired version of gnumed, then restore from the gnumed CCHIT test data, then upgrade

2. Lack of having implemented a non-doctor class of user (and associated permissions) may be one of the first things that would be needed for CCHIT.

_______________________________________________
Gnumed-devel mailing list
Gnumed-devel@...
http://lists.gnu.org/mailman/listinfo/gnumed-devel

Re: CCHIT - sql

by Jim Busser :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


On 2009-11-07, at 10:52 AM, Jim Busser wrote:

2. Lack of having implemented a non-doctor class of user (and associated permissions) may be one of the first things that would be needed for CCHIT.

From CCHIT test script:
2011 Test Script – Ambulatory + Child Health + Cardiovascular Page 2 of 1272011 Certification of Ambulatory EHRs October 27, 2009 © 2009 Certification Commission for 

Users
There must be five Physician type users with valid login. These users must have at least the following permissions: full access to all clinical functions. o Dr. Robert Alexander – Primary Care Physician in scenario 1 o Dr. McCoy - OB/GYN in scenario 2 o Dr. Internist E. Butler – Internist in scenario 3
o Dr. Jones – Internist
o Dr. Green – Cardiologist in CV scenario There must be one Nurse Practitioner type user with valid login. This user must have at least the following permissions: access to all clinical functions.
o Ellen Thompson, CFNP – for use in Scenario 1 There must be one Nurse type user with valid login. This user must have at least the following permissions: access to all clinical functions.
Proctor to update the Audit Trail Worksheet are highlighted in cyan
Child Health Certification or Cardiovascular Certification are highlighted in purple
items that are required ONLY for CV Advanced Reporting Capability Certification are highlighted in green
optional for 2011 are highlighted in yellow
Health Information Technology
There must be one Reception type user with valid login. This user must have access to only the following functions: registration and demographic functions.
There must be one Medical Assistant type user with valid login. This user must have at least the following permissions: access to all clinical functions. There must be one Office Manager type user with valid login. This user must have at least the following permissions: access to all clinical functions and
access to all information necessary to carry out test procedures 4.72 to 4.86. There must be one Security Administrator type user with valid login. This user must have at least the following permissions: access to all information
necessary to carry out security administrative tasks; no rights to access clinical data or Protected Health Information (PHI) as defined by the Centers for Medicare and Medicaid Services (CMS).
o See page 8374, section 160.103 Definitions in CMS site: http://www.cms.hhs.gov/SecurityStandard/Downloads/securityfinalrule.pdf

_______________________________________________
Gnumed-devel mailing list
Gnumed-devel@...
http://lists.gnu.org/mailman/listinfo/gnumed-devel

Re: Re: CCHIT - sql

by Karsten Hilbert :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Sat, Nov 07, 2009 at 10:52:52AM -0800, Jim Busser wrote:


> The CCHIT patients and their test data and the test doctors and
> other personnel would need to be created / entered and at the point
> where the test data had been entered, the data dumped and saved.

Well, this isn't really possible unless you are thinking of
entering them into a "clean" database and dumping that.

> This would greatly facilitate re-testing at any point in the future.

Absolutely.

> Caveats:
>
> 1. We would need, stored with dumped data, the version of the gnumed
> database to which it related since any new gnumed may choke trying
> to directly import it...

That is why it would be better not to have a dump but rather
have an SQL script *creating* those patients.

> 2. Lack of having implemented a non-doctor class of user (and
> associated permissions) may be one of the first things that would be
> needed for CCHIT.

Probably, yes.

Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD  4537 78B9 A9F9 E407 1346


_______________________________________________
Gnumed-devel mailing list
Gnumed-devel@...
http://lists.gnu.org/mailman/listinfo/gnumed-devel