A simple data model for an Electronic Medical Record
I present a simple data model for an EMR created using ARGO UML
Key components of this model:
- Patient – the person treated by the physician
- Physician – doctor
- Medication – drug prescribed for a diagnosis
- Encounter – a patient visit
- Diagnostics – what the physician deduces is wrong with the patient.
Relationships:
- 1:1 (one to one) – where one component can only be related to one instance of another component.
- 1:m (one to many) – where one component is related to several instances of another component
- m:m (many to many) – where several components are related to several instances of another component
Below is the model with comments alongside each object and each relationship
Health Internet vs NHIN: in pictures
I read with great interest, David Kibbe’s posting on the HealthCare blog, NHIN vs The Health Internet; that same week I also read Robert Rowley’s take on the NHIN vs The Health Internet. So I thought I would sum up the two perspectives with two pictures. (Forgive the delay, I took a break over Thanksgiving)
- NHIN – National Health Information Network – “is a collection of standards, protocols, legal agreements, specifications, and services that enables the secure exchange of health information over the internet.” Basically a Federal push for standards, specs and protocols to allow electronic data to be exchanged.
- HealthInternet – an open-market standards-based approach to enable the exchange and sharing of electronic health data, using existing Internet standard protocols and web technologies.
So here then a graphical view of the two approaches
-
Archives
- June 2010 (1)
- May 2010 (2)
- March 2010 (9)
- February 2010 (4)
- January 2010 (4)
- December 2009 (6)
- November 2009 (5)
- October 2009 (9)
- September 2009 (16)
- November 2008 (4)
- October 2008 (2)
- March 2008 (1)
-
Categories
-
RSS
Entries RSS
Comments RSS




