Software Development

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 }

Swift is a modern programming language created by Apple to make application development simpler.   Version 2.0 of the language is out and adds much needed error trapping/exception handling capability.   Swift is similar to other C-derived languages, and is easy to read for anyone familiar with Java or PHP.    My interest in Swift […]

{ 0 comments }

EHR Science and the Coming of Clinical Swift

by Jerome Carter on November 23, 2015 · 4 comments

As you may have noticed, for the last two weeks, resource pages have not been updated and there was no post last week either.  That is because a minor accident resulted in a week’s worth of misery, and not much work being done.  Thankfully, things are quickly returning to normal.  Oddly, one consequence of my […]

{ 4 comments }

Building Clinical Care Systems: Suggested Readings

by Jerome Carter on September 28, 2015 · 0 comments

This summer was very productive. I was able to jump into the human factors literature, test out BPM suites, and get into the nuances of Swift (more than a few). All the while, I have been reflecting on designing clinical software.   The really great thing is I have been able to experiment to my heart’s […]

{ 0 comments }

As I have written more about EHR design, I have noticed the term has different meanings among various groups focused on HIT. There are so many different groups focused on HIT — each with its literature and jargon — that at times it is difficult to communicate. The rising interest in user-centered design has made […]

{ 3 comments }

Everything changes.   The workflows from last year may not exist next year.   There will be new reporting requirements, new data elements, new forms, and new coding systems.   Creating software that grows gracefully with the times takes serious architectural thinking from the outset.   Vendor pain due to changing MU certification requirements makes the case that flexible […]

{ 4 comments }

As mentioned in the last post, I am exploring a new way of developing clinical software that puts processes front-and-center from start to finish. I call the approach informatics analysis and design, and it is the approach being used for my iOS project. Informatics analysis and design (IAD) assumes that real-world clinical care processes are […]

{ 0 comments }