Signing off 3000 documents does not need to take more time than is required to sign off 2 documents.
There is often a need for SOAPware providers who are the owners of documents to need to be able to sign off large groups of documents in one action. For example, in most clinics, paper documents come to the clinician's attention prior to having been scanned. The signs off the paper document and then the paper document (with the signature) is scanned into the electronic chart. Unfortunately, the emerging rules for electronic signature and the standard for the "Legal Electronic Health Record" are potentially in conflict with this workflow because there are requirements to have an electronic log of the date/times associated with signatures. The solution is to implement use of the Tasks Manager in a fashion so that the documents can be signed-off in a group, all at once, with a single action.
Establish work flows so that any documents that need to be signed in bulk have a common characteristic in one of the Tasks Manager columns. For example, it could simply be to select Sign as the option in the Action/Status column. Then, clicking on the Action/Status header will group all the documents that need to be signed.

Once the items that need to be signed-off as a group are clustered together, the next step is to select all of them. To do this, click on the far left of the first row.

Next, hold down the shift key and click at the far left on the last item in the group. Doing this selects all the items between the two clicks (while holding down the shift key).

Once all the items to sign-off are selected, then click on the Sign-off button.
![]()
This results in all of the selected documents being signed off in one action.
In SOAPware-2008 and subsequent versions, it is a bit easier. Simply drag the Action/Status Column up to the location of "Drag a colum header here to group that by column" and the items are instantly grouped for selection and sign-off.

Also, In SOAPware-2008, there is a new chart section called "Financial" where non-clinical documents (i.e. those not needing clinician signature) can be placed.
Important note: Before the scanning person or nurse sends the documents to the clinician's list for final sign-off, establish a workflow where that person changes the status in item in the task item so that the clinician can sort all the documents needing signing to all be in one place. This makes it possible to sign all of them in bulk without having to search around, etc. Over time, we will explores means as how to best automate the sorting of items needing sign-off and welcome suggestions.
For example, it does not seem logical to many clinicians that a scanned document containing their signature can't ensure EHR-S compliance. While this approach usually meets the state requirements for legal medical documentation, it is problematic meeting the emerging, national, legal, electronic record standards.
Please understand we are not making the rules, and can only make a best guess as to their final requirements. However, we are being proactive, and doing our best to help our users navigate the rocks hidden in the rapids. Much has been done, much is in process, and the workflow will be fine-tuned over time.
Actually, not having the clinician's date/time stamps has already resulted in some rather unpleasant legal outcomes of records challenged in court cases. Specifically, plaintiff attorneys have been successful in creating doubts whether or not the clinician ever even knew the information existed. There have been cases where clinicians have suffered from liability that could have been avoided by implementing workflow to prove that existence of documents had been verified, electronically. So again, it is wise to now create workflows so that all clinical documents have a date/time stamp as to when the clinician was aware of their existence. Again, this does NOT have to create more work, but does require some workflow changes.
Unfortunately, some of the workflows we now have to suggest may not initially seem logical for clinicians coming from a largely paper-based record (or SOAPware v4) environment, but are necessary.
This workflow is also necessary to support the emerging "legal EHR standard" or EHR-S. This standard is intended to eventually ensure that records are admissible under "Federal Rules of Evidence" by...
providing documents that are consistently and universally date/time stamped and have a clear source of substantiation for all business and clinical processes. The legal EHR standard creates a system of detailed accountability (e.g., audit logs, digital signatures, data encryption) that cannot be efficiently matched or mimicked in the paper world.
Any document containing clinical information needs the final, responsible clinician's date/time stamp in the electronic log indicating the clinician has recognized the existence of the document. The clinician's signature or initials on a scanned document does not create an adequate date/time stamp (going forward, but it did in the past). If a clinical document in an electronic chart does not have a date/time stamp indicating when it was noted by the clinician, this will create serious problems in the future.
Do NOT use Pulled Charts (i.e. as most do/did in v4) to manage tasks or to track what needs to be signed/completed. Use the Tasks Manager. Pulled Charts will NOT be able to track either actions needed nor reflect the actions that have been performed.
The industry is on the verge of a major shake-up due to the fact that many electronic medical record systems are not architected in a fashion to be able to meet the eminent, federal requirements. We have taken actions that appear likely to avoid what is likely to prove extremely problematic to many products and their users.
When I first heard of bulk signing, I thought it was a way to sign off documents that don't really need to be reviewed by a doctor--eg appointment reminder letters, or document already reviewed by the doctor and physically signed--eg home health forms.
In the former instance, there is no medico-legal need to show they were reviewed by a doctor, and in the latter, the scanned written signature (hopefully dated) fullfills that requirement.
In the scenario that seems to be described here, the provider is reviewing things on paper, then electronically signing them in bulk--documenting that he reviewed them at that date and time--except he didn't-- he reviewed them at an earlier date and time.
From a medico legal standpoint, it would seem best that if you review the paper, you sign the paper.
If you are going to bulk sign everything the scanning person flags as "sign", you had better trust your scanner. If you are going to handle labs this way, you should tell the scanner not to mark anything "sign" unless you have already initialed it. edited 04:37, 15 Oct 2008
My concern is with "bulk signing" When we incorporate that concept into our work flow, I think it is easy to get sloppy and start bulk signing documents that actually do require attention.
We are all sensitive to the legal ramifications of all of this, but in my books more important that this is patient care.
So in bulk signing we are relying on our staff appropriately assigning the correct status to these documents ie if they inadvertently assign a bulk sign status to an important document, we will sign it.
As it has worked in the past, my office staff finalize documents like cover letters, billing issues etc.
So if the work flow depends on them assigning the correct status to the document, why not let them sign off these documents and reduce workflow and the possibility of introducing errors. The more steps a process requires, (even if it is electronic) the more chance of introducing errors (I did not make that up).
I will start working with the task list to establish this work flow. However to date, 2008 has increased my work load significantly, not sure it has decreased my legal exposure, and it certainly has not improved my patient care.
jerome list md
PS: Analogue documents that come to the office are scanned and shredded. I do not review any paper documents. That has been a useful work flow for my office.
a)multiple page docs only create one item but have a page flipper (like V4) and one task to sign
b)give us the ability to create document folders in which a signature and task is optional, just adding a folder called financial is not sufficient,
c)address active provider/document owner situation, my clients with multiple physicians have always struggled with the need to change the active provider in a global location. i undersand that this may be needed to address the issue with printing documentation based on data fields calling for <active provider>. but if the document owner box was available for editing when a document is created then when a staff member who is in charge of large batches of document creation (scanning or importing) only has to be sure to set the document owner on the document they are creating this would be helpful in reducing errors.
d) assume the wrong active provider was selected at the creation of a scanned multipage document and the steps needed to correct are many, once you navigate to the document to re assign it each page in the container has to be changed inividually. very time consuming. maybe the ability to bulk change the owner would be helpful as well. if it is there I must be missing it.
e ) in 2008 when we have multiple items in an individual docutainer they all create a task and require signatiues, ie., a soapnote is created for a visit and we add a second soapnote to it to record procedure activity, then a lab that is specific to that visit and a copy of a scanned item such as an output slip from clinical device. before all of these items were signed off with one signature on the original container, the soapnote. now each item added creates its own task item and need to be signed. is this really necessary? it seems excessive.
i aplogize if some of these items seem to be in the wrong spot but they all pertain to signature activity.
tcicraig
There is still the issue that all pages of scanned documents create a separate task item making the task list larger. This will be addressed soon so that only one task list item is created for multi-page documents (i.e. default setting to scan all individual pages of an individual document to a single PDf and creating a single task item).
Also, a viewer is in development so that users can quickly scan through and directly view any individual items when signing multiple items.
You say that this does not have to be more work, only a different workflow. I think that is only partially true. In some cases it is true--whenever possible, we should review and sign documents electronically, instead of reviewing and signing on paper then scanning in, and having to electronically sign again.
But I cannot tell the hospital I won't sign my discharge summaries on paper because I am going to sign them in the office. So if I have to electronically sign them in my office after I signed them at the hospital, that IS extra work. I congratulate you on your efforts to MINIMIZE the extra work, but it is still extra work.
Question: Is it really necessary to treat that as part of the electronic record?? As I see it, that is a hospital record, for which the hospital is responsible. I am storing a copy in my office for my convenience. If someone requests a copy of my chart, I don't include that part--they have to get it from the hospital. So is it subject to the same requirements as internal documents? If not, please provide a section where I can store it without re-signing it.
For documents that have to go OUT on paper, it gets more complex. Home health sends me a 485, with an original nurse's signature, and I need to return it with my signature on the same paper as her signature. So I have to physically sign the paper in my office. But again, am I required to keep an electronically validated copy of that paper? Or can that be stored in my "convenience copy of outside records" section?
And what about appointment reminders and health maintenance reminders? Is it really necessary to prove I saw those letters?
Andy
The quick viewer for signing will help with both of those, by making it more practical to actually look at what we are signing, vs signing in bulk from the task list. But I'm afraid there will still be too much work in some cases.
If we are going to do any blind signing, our workflow needs to include steps to minimize the potential of the wrong documents being bulk signed. One step would be to limit it to certain chart sections, eg Correspondence Out, Hospital Notes (I use that section only for MY hospital notes, not outside notes). Another would be to require a signature process by the staff that sets it up for me to sign. If they set it for my signature simply by setting the Task Status field, I could end up signing a document just because somebody missed with the mouse by 1/8 inch when they meant to set that status to something else.
Andy edited 17:33, 21 Nov 2008
Trust me, we are not making the rules and are speaking up - http://www.modernhealthcare.com/apps/pbcs.dll/article?AID=/20081120/REG/311209995/1029/FREE&nocache=1&nocache=1 edited 17:49, 21 Nov 2008
Please note that HIPAA is very specific about what you must release if requested. ANYTHING YOU MAINTAIN IN THE MEDICAL RECORD must be released if the patient requests it, except for psychotherapy notes and drug & alcohol treatment. You CANNOT withhold hospital records, for example, or any other "outside" record, if you keep them as a part of your medical record. Trust me, I know--I've been busted by HIPAA for this before, and they ain't playin' around!
Dr. Oates,
I second the concerns of tcicraig. Hope you can address these issues creatively!
Thanks,
Jim
Actually, there are several other complicating issues when you have 50 states that go further than HIPAA and even conflict with each other at times. Add to this the fact that what worked for paper records of the past will not work for legal electronic records of the future. Combine this with the fact that confusion is present at all levels, and it really is challenging.
We will definitely have to be creative as we want acceptable workflows today that will not cause our users and us to be victims of the looming crises that is about to hit everyone who is not following the legal standards soon to be released. edited 01:14, 29 Nov 2008