Showing posts with label software. Show all posts
Showing posts with label software. Show all posts

30 June 2014

What inspired you to join the technology industry?

In theological circles, and especially in theological schools, there's a lot of talk around “call” and a sense of “calling.” But, ask a programmer about “call” or “calling” and you'll probably hear about using a functions or object-methods.

When I read about Google's Code School Learning Opportunity I knew I wanted to apply. Code School issues Open Badges!

The open-ended, final question on the application took me by surprise: What inspired you to join the technology industry? Wait a sec! Did a tech giant just ask about my “call story”? Yeah, I think so.

I have my doubts about whether a human at Google will actually read my application. If the filtering algorithm looks for compound and/or complex sentences, there might be a chance. However, I know there are humans that will read this post. So, I'll also share my technology “call story” with the handful of folks curious enough to click the link in an email or a Tweet.

A year and a half ago, I encountered an electronic health record system for the first time. After only a couple minutes in the consulting room, tense silence interrupted the usual, easy conversation. I watched, appalled, as my psychiatrist fought his way through the clunky, poorly sequenced fields of the e-prescribing interface. An engaged healthcare consumer, I quickly voiced my concern, mitigating the effect on our treatment relationship. This relieved the immediate anxiety I felt as a patient, but my concern as an advocate held fast. What impact would this technology have on those who already feel disempowered by the healthcare system? How would it affect the health of people at the margins of society?

A half-dozen years earlier, I'd left web application development to pursue a graduate degree in theology, focusing on social justice. The two fields scarcely touched, and in social justice theology, I found the kind of passion I'd seen—but, despite my aptitude, never experienced—as a programmer. Likewise, I scarcely looked back, even after leaving theological school without a degree.

That afternoon, as I watched technology that should have facilitated the provision of healthcare impede my doctor's work, these seemingly disparate and disjoint fields collided. During my theological study, I lacked a clear sense of “call” or vocation, but in that collision it began to crystallize. My “call” is neither in technology nor in social justice; my call is in both technology AND social justice.

That's it. …the short-version, at least.

Finally, share the link to the application form with others who might want to apply. And if you know a girl who's crafty, creative, or thinks technology is kind of cool, tell her to check out Made with Code, it's a pretty neat site (even if does have lots of pink).

09 November 2012

Web Feeds for Mental Health Advocates

Note: All feeds listed provide fee-free content, feeds with open-licensed content are indicated.

New to web feeds?

Web feeds—sometimes called newsfeeds or just feeds, often prefixed with the feed format (e.g. RSS, Atom), and usually (but not always) indicated with this [orange news feed icon] feed icon—are a great way to get information from several sources all in one place. To use them, you'll need a feed reader. A couple of my favorites are Google Reader (web) and Pulse (Android, iPhone/iPad, or web).

Blogs

LD News feed
Learning disability and childhood mental health news headlines with descriptions from LD Online (a service of Washington, DC PBS affiliate, WETA-TV).
Mental Healthcare Reform feed
National Council for Community Behavioral Healthcare
NAMI Blog feed
National Alliance for Mental Illness
Psychiatric News Alert feed
Psychiatric News; American Psychiatric Publishing.
The blog from the Psychiatric News sees new content most weekdays, and the feed contains full posts. Despite some redundancy, both the blog and the newsletter (below) are worth keeping an eye on. The newsletter contains information never posted to the blog, and blog posts sometimes contain information that doesn't appear in the newsletter until two or more issues in the future.
SAMHSA Dialogue Blog feed
Substance Abuse and Mental Health Services Administration, US Department of Health and Human Services.
Contains …up-to-date information including articles from SAMHSA staff, announcements of new programs, links to reports, grant opportunities, and ways to connect to other resources… (“About”, SAMHSA Blog.).
TWLoHA Blog feed & TWLoHA News feed
To Write Love on Her Arms

Journals and other Publications

Data, Outcomes, and Quality feed
Center for Behavioral Health Statistics and Quality, Substance Abuse and Mental Health Services Administration, US Department of Health and Human Services.
Reports and data sets related to behavioral health, mental illness, and substance abuse.
Depression Research and Treatment feed
Open-access (Creative Commons Attribution 3.0); Hindawi Publishing.
PLoS ONE Alerts: Mental Health feed
Open-access (Creative Commons Attribution 2.5); Public Library of Science.
Psychiatric News feed
Bi-weekly newsletter from the American Psychiatric Association.
This feed is updated when a new issue is published (alternate Fridays) and contains headlines (with links) for the latest issue.
Translational Psychiatry feed
Open-access (Creative Commons Attribution-Noncommercial-Share Alike 3.0 or Creative Commons Attribution-Noncommercial-No Derivative Works 3.0); Nature Publishing Group.
Contents for the current issue with link, author(s), and full citation.

03 May 2012

Thoughts on Software (lacking) Usability: Electronic Medical Records

This post is written in response to the post Globe article on EMRs: status and the safety issue on the e-patients.net blog.

The abundance of hard-to-use software is the only issue that repeatedly gives me reason to reconsider my decision to leave the programming field.

Here's my take on the origin of the problem:

In order to develop software with good (much less excellent) usability, the design process must include collecting data about day-to-day operations in the context where the software will be used. That rarely happens. Instead, the standard process is to meet with a ‘customer’ and discuss their requirements. Often, the ‘customer’ in that meeting is a management-level company representative with little personal experience with the nitty-gritty of those day-to-day operations and who will seldom (if ever) use the software that's being developed.

It's a poor substitute, at best, and leads to a functional but hard to use end-product. At best, the result is cream of the crap.

An better approach would borrow an number of methods, including participant observation, from cultural anthropology to gather data about how information is obtained, used, and communicated in day-to-day operations.

For EMR software, this would mean data collection in in various healthcare facilities. It would require following staff to observe information flow; perhaps even hands-on experience working in an information-saturated non-clinical role.

The executive rumored to have scoffed at the idea of usability as a criterion probably understood this—specifically, he probably understood the kind of time and resources (i.e. money) necessary to develop software specifications the right way. That is, he understood that it would cut into his bottom line more than he was willing to accept.

After all, the only thing with such amazing ability to trump common sense is concern for one's own wallet.