December 2015

The final installments: Clinical Workflow Analysis—More Useful than You Thought, IV Part IV: Intended Use and the Level of Detail Achieving Task and Workflow Interoperability in Healthcare, IV Part 4: Bridging the Gap Between Data and Workflow Achieving Task and Workflow Interoperability in Healthcare, V Part 5: Achieving Workflow Interoperability Among Healthcare Organizations

{ 0 comments }

After last week’s aside into the data vs. processes dilemma, it is time to get back to how one defines requirements for a clinical care system.  Requirements gathering has to proceed along a few different paths simultaneously, and for any completely new system, it is a messy activity.  There are four main requirement pathways: user […]

{ 0 comments }

Clinical Workflow Analysis—More Useful than You Thought, III: What to Analyze and Why – What are the most important questions to ask when analyzing workflows? Achieving Task and Workflow Interoperability in Healthcare–Part 3: Laying down a definition of workflow interoperability       

{ 0 comments }

Traditionally, clinical software has been organized around data.  The reason for this is the paper chart, which is a process-agnostic information source.  At the outset of creating a new software product, this question has to be answered early on: Is this a data-focused system or a process-focused one?  The architectural differences between the two types […]

{ 3 comments }

Clinical Process Management – The Patient in the Age of Processes A look at developing clinical process management as a structured approach to analyzing, modeling, and managing clinical systems. Achieving Task and Workflow Interoperability in Healthcare True interoperability requires sharing tasks in addition to data. Part 1: Achieving Task and Workflow Interoperability in Healthcare Part […]

{ 0 comments }