Search: "Clinical Swift"

Clinical Workflow Center Human factors methods are valuable tools for analyzing the nuances of clinical work.   Gaining familiarity with these methods can require a good deal of time and searching.   A new resource page has been added to Clinical Workflow Center to make life easier for those who want to begin exploring human factors techniques.   […]

{ 0 comments }

Clinical Workflow Center NIST and AHRQ have funded a collection of studies that focus on EHR-related clinical workflow issues. Overall, the reports contain useful information. However, there were a few things that I found puzzling. NIST and AHRQ Workflow Reports: A Few Observations Clinical Swift Inheritance is one of the cornerstones of object-oriented programming. Unfortunately, […]

{ 0 comments }

Either a programming language feature can be just what one needs or an obstacle to go around.  Swift provides features that make clinical software design easier. Tuples support clinical concepts cleanly, and Swift offers a good implementation. Thinking Clinically in Swift   Modeling clinical workflows with BPMN allows one to capture precise interactions. Using Level […]

{ 0 comments }

This Week on Clinical Swift

by Jerome Carter on April 7, 2016 · 0 comments

The prn: OnCall project is moving along well.   I have identified the main classes for the project and, in this week’s post, I review the rationale for each class along with a few other design decisions. Assembling the Class List for prn: OnCall

{ 0 comments }

This Week on Clinical Swift

by Jerome Carter on March 23, 2016 · 0 comments

Early on in the development process, most of the information gathered from future users consists of documents (e.g., forms, policy/procedure) and interview data (e.g., feature descriptions, desired functions, specific dislikes, wish-list items, etc.). As a software designer using object-oriented design, the next major step in making this information actionable is capturing how users will interact […]

{ 0 comments }

This Week on Clinical Swift

by Jerome Carter on March 18, 2016 · 0 comments

What does an entry in a chart (paper or electronic) mean? How should an entry be interpreted? These may seem like odd questions; however, when designing a clinical system, such issues come up more often than one might expect.    They are especially pertinent when migrating data from one system to another (and it is not […]

{ 0 comments }

This Week on Clinical Swift

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 […]

{ 0 comments }