Will the Apple iPad Force Healthcare to Finally Abandon Outmoded User Interface Designs?

Short Link: http://j.mp/cbQP2c

I can’t leave the iPad alone, literally or figuratively (how many EMR users can say *that* about their EMR?). Last week I explored the relationship between EMR/EHR/clinical groupware contextual usability and process awareness. This week I consider the following apparent contradiction:

Most reviewers agree that the iPad is optimized for content consumption, not content creation.

“The iPad is not a laptop. It’s not nearly as good for creating stuff. On the other hand, it’s infinitely more convenient for consuming it — books, music, video, photos, Web, e-mail and so on. For most people, manipulating these digital materials directly by touching them is a completely new experience — and a deeply satisfying one.” (Looking at the iPad From Two Angles, David Pogue)

However another article reports that of all industries healthcare is most agog at the iPad’s form factor and usability.

“So while the rest of the world texts, tweets, and generally fawns over the thing, that’s muted compared with the reception the iPad is getting in the health care universe…This isn’t just hot-new-toy fever sweeping the mediverse, though: If the iPad becomes as ubiquitous in medical facilities as the iPod is everywhere else, it could usher in literally billions in savings.” (An Apple a Day: Will the iPad revolutionize health care?, Martha White)

The apparent contradiction? Physicians need to create content at the point of care, not just consume it. They will resist hauling around multiple devices. While the iPad has a virtual keyboard and an optional keyboard accessory, and there’s Dragon Dictation, clicking (or in this case, tapping) to perform routine data entry is not likely to go away.

But consider the following blogosphere comment:

“I have read reports from ‘excellent’ EHR systems…which contain disastrous errors created by a 0.5 mm slip of the mouse pointer and a click. This is what happens when two opposite diagnoses differ by one consonant and are adjacent in the pull-down list. We are trying to treat the patient but we are really doctoring the EHR.”

And (in reaction to the iPad):

“Even most template driven EMR software would not be fun on an iPad. Checking a check box with touch can be painful if the check box is too small, no?”

Absolutely right and exactly my point. The Cognitive Psychology of Pediatric EMR Usability and Workflow starts with a question and graphic example of the issue.

“Which targets are easier to hit quickly, accurately, and repeatedly? Small checkboxes or large buttons?”

fitts-law-checkboxes-vs-large-buttons

Figure 1: See Post Script.

The answer is obvious. There’s even a psychological law.

Fitts’s Law: “The time required to rapidly move to a target area is a function of the distance to and the size of the target.” (Wiki article on Fitts’s Law)

For user interface design, Hick’s Law complements Fitts’s Law:

Hick’s Law: “The more choices you have to choose from, the longer it takes for you to make a decision.” (Wiki article on Hick’s Law–you’ll have to copy and paste “http://en.wikipedia.org/wiki/Hick’s_law” into your browser, WordPress doesn’t handle apostrophe’s in links well)

“Acquiring” (human factors speak for click or tap) one small “target” amidst many “competing” targets is slower, more effortful, and error prone than a large target among just a few alternatives.

How, might you ask, can EMRs, EHRs, or clinical groupware present *enough* buttons to their physician users so they can enter all the data and orders that they need? Instead of just a few big screens containing many small buttons and checkboxes and so on, spread larger buttons (and no checkboxes, not a one) across many screens.

How, might you ask, are you expected to navigate to the right screen at the right time to click on the right button? For each specific context (well child visit, sick child visit, vaccination, etc.) present the right screens in the right sequence to the user in a way that mirrors the natural order of the tasks the user needs to accomplish. That was my major point in last week’s post Contextual Usability, My Apple iPad, and Process-Aware Clinical Groupware for Pediatric Practice.

The iPad and similar devices may indeed transform digital medicine. If they do, one important reason will likely be that it forces EMR, EHR, and clinical groupware developers to get rid of those cramped rows of itty-bitty little checkboxes and endlessly scrolling lists of skinny pick list items. To do so requires clinical groupware to ask and answer the right question at the right time and act appropriately, to hand to the user the right data or order entry screen with all, but only, the right data or options. I don’t see any other way for clinical groupware to do this than to rely on some form of user-programmable executable process model.

P.S. Read about post-WIMP (Windows, Icons, Menus, Pointer) user interfaces.

P.S.S. Follow me on Twitter at @chuckwebster.

Posted in EHR Workflow | 10 Comments

Contextual Usability, My Apple iPad, and Process-Aware Clinical Groupware for Pediatric Practice

Short Link: http://j.mp/dbhBvw

Apple started selling iPads today. I bought one. I published this post from it.

There’s an important relationship between

  • iPad-like form factors, task-at-a-time workflow, and contextual usability in mobile settings on one hand and
  • process-aware clinical groupware for pediatric practice (AKA pediatric EMR workflow systems) on the other hand.

I’ll use as a springboard Todd Biske’s Context Aware Computing and the iPad (please read the original!) in which he writes (though I’ve replaced “meeting room” with “exam room”, “meeting” with “patient encounter”, and “subject of the meeting” with “type of patient encounter”):

“Now, we have the potential for device with a larger form factor that can present a touch-based interface, completely tailored to the task at hand…Imagine going into an [exam] room where your iPad is able to determine your [exam] room…where it knows what [patient encounter] you’re in and who else is in the room…it knows the [type of patient encounter], and can now present you with a purpose-driven interface for that particular [patient encounter]…How many times have you been in a [patient encounter] only to wind up wasting time navigating around through your files…trying to find the right information. What if you had an app that organized it all and through context awareness, presented what you needed?…As we have more use of BPM [business process management] and Workflow technologies, it is certainly possible that context awareness through location, time, presence of others, and more can allow more appropriate and efficient interfaces for task display and execution, in addition to providing context back into the system to aid in continuous improvement.” (my emphasis)

Compare Todd Biske’s account of contextual awareness with a quote from my own 2005 HIMSS proceedings paper about EHR workflow management systems. EHR workflow management systems use specialty-specific process definitions to create specialty-specific clinical groupware, such as pediatric EMR workflow systems. Pediatric EMR workflow systems combine pediatric-specific screen and screenless components into modules and perform (“enact” in workflow automation terminology) pediatric workflows for pediatricians, staff, and patients:

“The process definition saves the user from having to navigate manually through a thicket of menus, tabs, or popup lists; the EHR presents the correct screen given the context of the user’s tasks. If an EHR can be instructed (that is, customized) in what to do—automatically—based on who, what, why, when, where, and how, the EHR is not just a patient documentation system, it is an EHR workflow management system….Process definitions are used by the workflow engine in a similar way to rules being used by an expert system. The workflow engine reasons about who, what, why, when, where, and how in order to save the user work. Who is the user? (Dr. Jones or Dr. Smith?) What is their role in the office? (Physician, nurse, technician?) Why is the patient here? (Well child? Chronic disease management?) When is ‘now’, relative to what has been accomplished and what remains? Where is the user? (Exam room? Tech station?) How does this specialty accomplish its tasks? Each step in the process definition corresponds to a specialized data presentation, acquisition, or transformation task. The process definition describes the event that triggers the presentation of the screen as well as a context that informs its content and behavior. For example, the Review of Systems screen allows the nurse to do just that, review the patient’s systems. It is triggered by the completion of the preceding screen (or by the nurse logging into the EHR in the exam room in the presence of the patient after all the preceding tasks in the process definition have been accomplished).” (my emphasis)

Todd Biske writes about business meetings and I pediatric ambulatory encounters, but we address the same thing: contextual usability. In conversation (though this is the first time I’ve blogged about it) I often refer to what I call my journalism theory of usability. Journalism is all about context. To achieve contextual usability clinical groupware needs to ask itself the same questions journalists ask themselves to write compelling and useful news reports—who, what, why, when, where, and how? Automated answers to these questions drive context-aware automatic behaviors, such as offering the right screen at the right time and place or accomplishing useful tasks in the background without need for human intervention.

Biske also refers to “providing context back into the system to aid in continuous improvement.” This is business process management’s (BPM) “process optimization process.” Process-aware clinical groupware is more systematically improvable using business process management techniques than EMR/EHR/clinical groupware without process models (which is most). From a recent post intended to be something of a manifesto:

“The only practical means by which [systematic improvement] will be achieved will be if modular EMR/EHR/clinical groupware systems also include within their very technological nature the ability to systematically change internal processes and workflows to better meet set objectives while working in typical environments.” (Usable Clinical Groupware Requires Modular Components and Business Process Management)

A workflow engine executing process definitions (an “executable process model”) makes it possible for clinical groupware to automatically present the right screen, data or order entry options, and presentation format at the right time and place in pediatric workflow to save pediatricians time and concern. The workflow engine automatically does the right thing at the right time and place because it consults a process model, that is, the set of process definitions that model pediatric workflow and processes for a particular pediatric office. The executable process model makes clinical groupware both context aware *and* flexibly so (that is, editable by users, without the special technical knowledge of a computer programmer).

If a pediatric task languishes beyond customizable parameters (such as duration), it automatically escalates to the attention of a care coordinator or physician. The “severity” of the escalation (such as passive visual cue versus pop-up alert that requires dismissal versus flashing red lights and a siren) and to whom (user versus supervisor versus emergency response team) are also part of the executable process model. Tasks are escalated in a manner that is contextually appropriate because the process model represents actionable knowledge about escalation context and is under control of clinical staff who understand this context.

So, all hail process-aware/context-aware, EMR/EHR/clinical groupware! And especially for fast paced, but frequently interrupted, pediatric workflow in pediatric ambulatory settings.

Reference

Contextual Usability: Rigour meets relevance when usability goes mobile, Lindroth & Nilsson, 2001.

P.S. A long quasi-personal note: The Apple iPad is programmed in Objective-C, which was developed by Brad Cox, a graduate (Ph.D. Mathematical Biology) of my alma mater, the University of Chicago. For C# programmers there’s MonoTouch, which still requires a Mac to deploy to the iPad. I encountered object-oriented languages such as SmallTalk (Objective-C combines features of the C and SmallTalk programming languages) while a graduate student in Industrial Engineering at the University of Illinois and then medical student at the University of Chicago (through an elective course in the Department of Mathematics). I was interested in simulating biological systems embedded in simulated social systems. Techniques for doing so have potential for simulating (and understanding) changes in patient clinical state within simulated (and understood) socio-technical systems for improving patient clinical state. Sounds theoretical, right? However, there are potential practical applications of this approach for systematically improving clinical outcomes, patient satisfaction, and practice productivity. The key is to take a complete systems engineering view of the pediatric medical home. As an industrial engineer, I was already familiar with the use of FORTRAN for discrete-event modeling and simulation of patient flow through medical offices, emergency rooms, and hospitals. One such project at the university health clinic paid my tuition and stipend for one year during graduate school. Object-oriented programming languages are a natural for simulating complex systems (the EncounterPRO Pediatric EMR Workflow System uses object-oriented technology to achieve its highly componentized and modular platform architecture). I later considered use of Objective-C for simulating patient flows in a medical office combined with a Markov model of evolution of patient clinical state (a now standard technique). Every interesting idea does seem connected to every other interesting idea, in a six-degrees of separation sort of way. Objective-C influenced design of the Java programming language for which I eventually certified as a programmer. I recently developed some simulations of pediatric patients flowing through pediatric clinics (based on actual, though deidentified, data using workflow/process mining techniques, I’ll blog about it soon). Wouldn’t it be cool to run it on the iPad? The point being to give a pediatrician or primary care physician a tool to understand and improve patient flow through their office. (Warning! flight of fantasy ahead!) And then climb in a time machine to go back and hand it to my past-self! Of course, I don’t remember anyone materializing in front of me with an iPad, so the time machine part probably won’t happen—fun to think about though! Regardless, the iPad’s form factor, task-at-a-time workflow, and contextual usability make it a great user interface for the process-aware clinical groupware I advocate, for busy pediatricians or any high-volume, low-margin ambulatory specialty. By the way, we also have Brad Cox and Objective-C to thank for paving the way to modular component-based clinical groupware.

From the Wiki entry about component-based software engineering (IC = Integrated Circuit, such as the memory sticks you click into PC and laptop slots to add memory):

Brad Cox of Stepstone largely defined the modern concept of a software component. He called them Software ICs and set out to create an infrastructure and market for these components by inventing the Objective-C programming language.

P.S.S. Follow me on Twitter @chuckwebster.

Posted in EHR Workflow | 2 Comments

Clinical Groupware as Clinical Teamware for Pediatric and Primary Care Practice

Short Link: http://j.mp/bUmHkC

A great pediatrician or primary care physician (family medicine, obstetrics & gynecology, or general internal medicine) is caring, attentive, available and knowledgeable; a great pediatric or primary care office is full of people with these qualities; and a great pediatric or primary care EMR/EHR (electronic medical/health record) allows the doctor and staff to show what makes them great. For example, being able to express a caring persona by adding an alert to a child’s record (reminding to ask about Tigger, the family cat) may seem like a small thing, but the family sees this as a good quality.

Key to supporting a great pediatric, family medicine, obstetrics & gynecology, general internal medicine team is a new kind of EMR software, called clinical groupware. In contrast to traditional EMRs and EHRs based on a “singleware” approach, clinical groupware is

“intentional care team processes and procedures pertaining to the observation and treatment of patients plus the tools designed to support and facilitate the care team’s work.”

Clinical groupware could be called clinical “teamware,” since it helps you coordinate your work with your staff and with other primary care specialists or subspecialists as part of a high performance medical home. It frees resources, manages interruptions, and reduces distraction to help you better know, care, and attend to your patients.

How does clinical groupware do this?

encounterview21

Large Colorful Buttons Help Navigation
and Data Entry Using Peripheral Vision

Let’s consider the remaining adjectives that apply to a great pediatric or primary care office: attentive, available, and knowledgeable.

Clinical Groupware Allows a Primary Care Physician to be More Attentive

One Georgia pediatrician, winner of the HIMSS Davies Ambulatory Care Award of Excellence (the most prestigious award for use of an EMR), shows his attentiveness using one hand to steady an energetic child and the other hand to enter data and orders out of the corner of his eye, made easy by large colorful buttons. A workflow engine pushes screens in preprogrammed sequences so he is not distracted by screen-to-screen navigation. Workflow-driven clinical groupware allows him to enter orders and automatically add work items (such as assembling educational materials or vaccination trays) onto staff to-do lists without interrupting patient-physician interaction. His focus remains uninterrupted and attentive to the concerned parent. Families like to see the doctor focus on them.

Clinical Groupware Allows a Primary Care Physician to be More Available

Taking a call from a patient and accessing an EMR from home is powerful availability. Spending more time with each patient is another form of availability. Clinical groupware makes a primary care office more efficient through (1) automated workflows and (2) keeping staff constantly aware of what you, the physician, are doing and intends to be done as well as keeping you aware of they are doing and their outstanding tasks. Clinical groupware makes “shared situational awareness” possible. Another Chicago pediatrician, who also won the HIMSS Davies Award, notes that customizable workflow has made his office so much more efficient that he can see more patients and spend more time with each patient. Efficiency frees time to be more available to parents and patients.

Clinical Groupware Helps a Primary Care Physician be More Knowledgeable

Obviously, a primary care physician should be perceptive and know his or her medicine. Conveniences include reminders of needed immunizations, a graph of growth relative to a norm, and a calculated drug dose. But there is something even more important: a pediatric, family medicine, obstetrics & gynecology, general internal medicine EMR should show the physician, at a glance, patient assessments, problems, flow sheets, current medications and treatments. For example, the EncounterPRO EMR (“Clinical Groupware for Pediatric and Primary Care”) filters the SOAP note to display relevant information, while allowing access to all information with the touch of a button. When the physician can, at a glance, “know” a child, mother-to-be, or other family member’s current information, this is the most important kind of knowledge of all.

Briefly turning to pediatric-specific functionality (EncounterPRO was the first Windows-based pediatric EMR for physician offices, debuting in 1995), EncounterPRO includes: premature, infant and child growth charts; vaccination tracking; functional development; Barton Schmitt pediatric protocols for telephone triage; and direct integration of vitals and spirometry instruments from Midmark Diagnostics Group and Welch Allyn. Areas of the record can be configured to be inaccessible by patients or guardians. Pediatric-specific reporting includes School Immunization, School Absence and Camp forms; Parent Take Home, Overdue Health Maintenance and a variety of signed immunization reports. The documentation for a HEDIS audit is as simple as the touch of a button.

The vaccine tracking and management module of the EncounterPRO EMR has interfaces to state immunization registries (in those states that offer an automated upload option) as well as direct parent signature capture in exam rooms. The module relies on CDC guidelines for notification of when a patient is due for a specific vaccine and recommends a schedule of the remaining doses. It works for patients who are on schedule as well as those who have fallen behind. Access to the CDC guidelines is quickly available.

Clinical groupware is about more than just coordination of care; it is about coordination of knowledge too. An important feature of clinical groupware is the ability for specialists to create and manage new knowledge about what works and doesn’t work and share it with each other. For example, for new and useful reports and workflows created or customized locally, users should have the option of sharing with a larger community at other clinical groupware sites (see Addendum for further discussion in context of vaccine management).

Clinical Groupware Provides a Different Experience than Traditional EMRs

Family medicine, obstetrics & gynecology physician Dr. Jeffrey Harris wrote in his winning HIMSS Davies application (achieving a third win of the HIMSS Davies Award for a clinical groupware EMR):

“The EMR user interface is akin to the touch screen-oriented systems in restaurants: one screen at a time, with only the most relevant data displayed and options presented (although, of course, a user can always jump out of a particular screen sequence to accomplish an arbitrary task), and the sequences can be tweaked through the workflow management to make such occurrences infrequent…The workflow plans are tailored for each type of patient seen in the office (obstetrics, gynecologic, annual exams, family practice) assuring that key elements of the present illness, history and physical are addressed and documented. Work plans contain required laboratory tests for specific conditions, assuring that key tests are not forgotten.” (Dr. Jeffrey Harris, MD, Family Practice, Obstetrics & Gynecology)

Workflow-driven clinical groupware provides a different user experience than the clickity-clickity-click-click-click, hunt-and-peck style of interaction with traditional EMR singleware. In an EMR workflow system the computer is the workflow engine, not the physician.

Clinical Groupware is Ideal for High-Volume, Low-Margin Specialties

EMRs based on clinical groupware are ideal for any high-volume, low-margin ambulatory medical specialty. While close to 70 percent of EncounterPRO users are pediatric practices, about 25 percent are family medicine and obstetrics & gynecology. EncounterPRO users in all of these settings have won the most prestigious award for use of an EMR, the HIMSS Davies Award.

Family medicine physicians, obstetricians, gynecologists, and general internists have a lot in common with pediatricians. They all operate with narrow profit margins. Reducing costs, capturing charges correctly, and increasing the number of encounters can increase profit. For example, if a pediatrician cannot chart a routine otitis media encounter from start to finish in 30 seconds, the EMR will slow him or her down and reduce profit. Clinical groupware workflow engines push tasks to users as fast as they can perform them. Family medicine and obstetrics & gynecology versions of clinical groupware rely on family medicine- and obstetrics & gynecology-specific process definitions to tell workflow engines to push family medicine- and obstetrics & gynecology-specific tasks in family medicine- and obstetrics & gynecology-specific-sequences to achieve workflow automation induced productivity surges, decreasing encounter length and increasing patient volume.

Flexible Automatic Workflows plus Shared Situational Awareness

Clinical groupware emphasize flexible to-do lists and task tracking. Yes, many traditional singleware EMRs have to-do lists and task tracking, but they are not flexible. Their workflows are, in a sense, “frozen.” A clinical groupware workflow system has a workflow engine that automatically executes modifiable workflow definitions to save users time and effort. You don’t like your workflow? Change it! You can’t do this with traditional EMR singleware.

Various clinical groupware communication and follow-up tools assist a pediatrician, primary care physician, and the entire office team to better manage patients and tasks throughout the office. Visitors to office sites often comment on the quiet efficiency with which a clinical groupware-equipped office runs—the workflow system reduces the need for constant staff interaction about what needs to be done. Automatic task delegation to the right staff person, performed by a workflow engine executing a process definition, gets the job done.

office-view1

Office View Tracks Patient, Task, and Provider Workflow in Real Time

Pediatricians and other primary care physicians and staff often struggle with office flow. Where are the patients? Where are the doctors? Where are the nurses? The EncounterPRO EMR Office View lets users see patient location, which provider the patient is scheduled to see, tasks ordered for the patient, who is responsible for performing the tasks, and how long each task has been outstanding in minutes (updated continually in real time) – all in one multi-color coded screen. Usability engineers (the technical folks who make sure software is usable) call such screens “radar” views, because they resemble the radar screens in airport control towers. When every one of the staff can see a radar view of each other’s location and patient tasks the result is what usability engineers call “shared situational awareness.” In other words, EncounterPRO’s Office View tracks patients, tasks, and staff to make sure everything flows nicely and without collision.

Nurses can easily identify unaccomplished patient care tasks. The office view helps staff manage higher patient volume more efficiently. Nurses can see patients in a real-time virtual waiting room and monitor phone calls posted in a telephone message room. In some offices, the office view screen (shown), waiting room view screen, and telephone message room view screen each has its own dedicated flat monitor, easily observed by any nurse or physician, to monitor progress and facilitate moment-to-moment workflow where necessary.

Clinical Groupware Improves Your Bottom Line

Implementing a pediatric, family medicine, or obstetrics & gynecology EMR workflow system has a big payoff. Average income per physician can increase substantially after implementation. Flexible and coordinated workflow, streamlined navigation and communication, and easy-to-create accurate documentation lead to seeing more patients, spending more time with each patient, or going home early (the particular emphasis depending on your own business or personal objectives). One solo pediatrician HIMSS Davies Award winner, and EncounterPRO EMR user, doubled his income by seeing more patients and overseeing more clinical staff who see more patients.

A good pediatric and primary care EMR has the necessary pediatric-, family medicine-, obstetrics & gynecology, and general internal medicine-specific screens, functions, and reports. A great pediatric and primary care EMR must be more than its parts. Clinical groupware for pediatric and primary care practice must and does maximize opportunity for pediatricians, family medicine physicians, obstetricians, gynecologists and their staff to demonstrate care, attentiveness, availability and knowledge—while making excellent business sense.

Clinical Groupware and the Multispecialty Medical Home

If you are a pediatrician, family medicine physician, obstetrician, gynecologist, general internist, or other primary care subspecialist, why should you care whether EMR/EHR groupware can handle the other primary care and related specialties?

To future proof your practice.

  • You may eventually add another primary care specialty to your list of board certifications (some EncounterPRO users are board certified in multiple specialties). EncounterPRO’s specialty-specific automated workflows will switch specialties when you do.
  • Your practice may add a primary care physician who will complement your own specialty (many EncounterPRO users work in multispecialty primary care settings). Specialty-specific workflows will allow you and your partners to each “Have It Your Way” while not stepping on each other’s toes.
  • You may need to communicate and coordinate with other primary care specialists who join your practice, or other specialty-specific EMRs outside your practice as part of a high performance medical home. If so, your EMR will need to “know” more than just your specialty.

If you think any of these events may happen in your future, please consider getting a clinical groupware solution used by thousands of users, including primary care physicians in pediatrics, family medicine, obstetrics & gynecology, general internal medicine, and physicians in primary care-related subspecialties.

Summary

Clinical groupware for pediatric and primary care practice is a new kind of EMR software. It speeds up data review and entry, order entry, and coordination between you and your staff, to allow your clinical team to be great. By increasing efficiency and effective coordination among you and your staff, clinical groupware manages interruption, reduces distraction, and frees resources to make you more available to better know, care, and attend to your patients.

Addendum: Clinical Groupware Sharable Content and Behavior (Vaccine Management Example)

Recall the definition for clinical groupware:

“intentional care team processes and procedures pertaining to the observation and treatment of patients plus the tools designed to support and facilitate the care team’s work.”

“Pertain” is a mighty big and elastic word. Clinical groupware is about more than just executing “process and procedures pertaining to the observation and treatment of patients.” It is also about groupware approaches to designing, creating, managing, improving, and sharing process and procedure knowledge within a community of users.

I’ll use vaccine management as an example of what I mean.

Debuting in 1995, the EncounterPRO Pediatric EMR had the first rule-based vaccine tracking module embedded in a complete pediatric EMR system. By “complete” I mean (back then) an EMR that enabled a pediatric practice to eliminate paper, except for that scanned in from the outside world or which needed to be printed back at it (not bad for the midnineties).

The EncounterPRO Pediatric Workflow System uses a set of rules, based on CDC immunization schedules, to calculate if a vaccine dose is due, when the next dose is due, and complex catch-up schedules for older children (such as adoptees from countries with different schedules or for whom immunization history is not known). Vaccine schedule logic is “soft coded,” not hard coded. With respect to the H1N1 vaccine, we did not release a new version of EncounterPRO. All that was required was editing of the existing vaccine schedule rules.

We used to “dial in” to edit the rules, but now we can edit our master database in Atlanta and “sync” new vaccine scheduling rules out to our customer sites. In the latest version of the EncounterPRO Pediatric EMR the local pediatrician can also create and edit his or her own vaccine schedule rules. So, whether we automatically sync out new vaccine schedule rules from our master database in Atlanta, or the local pediatrician makes a local copy and edits them directly, there is no need to release and install a new version of the EncounterPRO Pediatric Workflow System software just to cope with new vaccines and changes in recommended uses of established vaccines.

Pediatricians can also edit and publish vaccine schedules, uploading their efforts to an online library to share with other pediatricians. By this means, one pediatrician can update vaccine scheduling rules when they change and make the updated vaccine schedule available to other pediatricians.

Clinical groupware with the ability for users to study, change, improve, and share EMR content and behavior resembles, in some respects, an open source community. What makes this possible is the user-programmer (has the ring of “citizen-soldier,” to which there may be an apt analogy). EHR workflow management system and business process management technology bring to clinical groupware the possibility that the clinicians who use clinical software will make it do what they need and want without reliance on well-meaning C#/Java programmers who can never completely understand clinical requirements.

Posted in EHR Workflow | Leave a comment

Copyright Received for EHR Workflow Management Systems Criteria

Short Link: http://j.mp/cmsisv

I received a cool looking document last week, the copyright certificate of registration for the EHR Workflow Management Systems survey of features and functions.

copyright-seal-web

A fan of open source and open minds, I license everything on this blog (and we everything on our product website) under the Creative Commons Attribution 3.0 License.

creative-commons

I essentially registered the copyright to give you (or anyone) the right to adapt and use the EHR workflow management survey criteria (with attribution, of course!).

copyright-web

So, please feel free to use or adapt and use the EHR Workflow Management Systems survey of features and function for any purpose whatsoever, knowing that you have the right to do so.

Have fun!

Posted in EHR Workflow | Leave a comment

#HIMSS10 Best Ever: Due in Large Part to Social Media

Short Link: http://j.mp/9GEhUr

“#HIMSS10” was the hashtag used in tweets about this year’s HIMSS conference in Atlanta, March 1-4. Attendees searched Twitter for #HIMSS10 to follow a gigantic conversation. #HIMSS10, or more precisely the convergence it symbolizes to me, transformed my HIMSS conference experience.

I’ve been coming to HIMSS conferences for ten years. The added social media dimension improved my #HIMSS10 experience in three ways:

  1. Blogging, Twitter, Facebook, LinkedIn, and so on, are all relatively new and interesting to me. HIMSS session content on these subjects was superb. In particular, Twitter 101 and the three Meet the Blogger sessions (delivered and moderated by Cesar Torres, respectively, and facilitated by Ward Seward, both of HIMSS) were high points. I’ve been blogging for a year and tweeting for a couple months, but I’m still a newbie, which is great, because learning (and sharing) is so much fun.
  2. All the HIMSS sessions I attended (not just the social media sessions) were embedded in a dynamic, interactive, virtual matrix of back-channel chit-chat that entertained and provided valuable real-time annotations to what I observed at the podium. It was tonic that kept me awake (even after lunch or at the end of a long day) and provided a steady stream of valuable information (and links to valuable information) that I archived and, even now, as I write this post, consult.
  3. Representing my blog (chuckwebster.com) and twitter account (@chuckwebster), I came to HIMSS with new motivation to absorb, connect, and take away as much as I could, so that I can turn around and think, write, and interact about that content as much as I can. I’m not a reporter. I don’t have press credentials, but I felt a little bit like one. Each time (which was rare) my attention began to lag, I’d mentally slap myself, so as to not miss anything important, so as to not misattribute or misquote someone, so as to maximize the number of juicy new ideas to combine with my own.

I have a new measure for HIMSS conference success: the number of new ideas I gain for future blog posts. By this measure #HIMSS10 hit it out of the ballpark. My ideas-for-future-posts.txt file just doubled. Of course, this number is only a coarse and indirect measure of something else, something more profound, involving learning, communication, and self-concept.

A short anecdote:

I wore a red carnation and tweeted this. A couple days later, while I’m walking the exhibit floor, I hear “Hey! You’re the guy with the carnation!” Well, yes I am. Do you follow me on Twitter? “No” Do you read my blog? (I stream tweets there) “No, I’ve just been reading all the tweets that contain #HIMSS10, and I remember one that said something like ‘I’m wearing a carnation, stop me if you see it,’ so I did.”

Splendiferous!

P.S. Follow me on Twitter at @chuckwebster

Posted in EHR Workflow | Leave a comment