Explorations in the Design and Implementation of Clinical Information Systems
by Jerome Carter on March 11, 2016 · 0 comments
Requirements are needed to build systems. Functional requirements state what a system should be able to do (i.e., the features/functions users request). Non-functional requirements address system qualities such as usability and security. This week’s post moves the prn: OnCall project forward with the version 1.0 of the feature list and a few final musings on requirements.
prn: OnCall–Features and Non-Functional Requirement Concerns
Previous post: This Week on Clinical Workflow Center
Interested in clinical workflow analysis, modeling or applying workflow to CDS, safety, usability, optimization, or software design?
12/14/16 - Managing Patient Communications with Workflow Technology, Part IV: Conducting the Workflow Analysis
10/10/16 - Managing Patient Communications with Workflow Technology, Part I
The EHR Science Blog presents the musings of Jerome H. Carter, MD, CEO of Informatics Squared, Inc.
Dr. Carter is the editor of Electronic Health Records, Second Edition, published by the American College of Physicians.
Posts on this blog are the personal views of Dr. Carter and do not reflect the official policies or positions of the American College of Physicians.
Primary Care—Leading the HIT Revolution, Part I: Supporting Clinical Processes
Usability Research: The Need for Standards
Is the Electronic Health Record Defunct?EHR Malpractice—Coming to a Location Near You?
EHR Design: Default Values as a Cause of ErrorsCopyright © 2011-2015– Informatics Squared, Inc. All Rights Reserved
Images Licensed from iStockPhoto
{ 0 comments… add one now }