From 34ac0f73276d154f509071a6a12d819667f155e7 Mon Sep 17 00:00:00 2001 From: toby cabot Date: Thu, 5 Jan 2012 17:42:46 -0500 Subject: [PATCH 1/4] typo: partied -> parties --- standardization.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/standardization.html b/standardization.html index 9cf1cf8..971530f 100644 --- a/standardization.html +++ b/standardization.html @@ -42,7 +42,7 @@
hData at HL7 and OMG

The HL7 Architecture Board decided that the SOA Working Group would be best suited to manage the hData projects at HL7. Other - interested partied include the ITS Working Group, Modeling and Methodology, and the + interested parties include the ITS Working Group, Modeling and Methodology, and the Security Working Group. hData has its own wiki page on the HL7 wiki.

Within OMG, the hData RESTful Transport specification has been submitted for consideration as an OMG specification using the (fast-track) RFC process.

From 9ecf77fdf8f75af7030e4ccdb3910e3159213148 Mon Sep 17 00:00:00 2001 From: toby cabot Date: Thu, 5 Jan 2012 17:43:06 -0500 Subject: [PATCH 2/4] typo: tbe -> the --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index 744b0b7..e175c71 100644 --- a/index.html +++ b/index.html @@ -16,7 +16,7 @@

The hData specifications have been submitted to Health Layer 7 (HL7) and and the Object Management Group (OMG) for standadization. The hData Record Format is on the normative track at HL7 and has recently passed the DSTU ballot. More information can be found in the Standardization page.

What is the hData design philosophy?

-

hData is designed for ease of implementation and improved efficiency by reducing the size of the data set, implementing a single way to represent data, and using standard web best practices. Crucial to achieving these design goals is a clear separation of content and exchange specifications. For this, the HL7 hData Record Format defines tbe concept of a hData Content Profile (HCP), which allows the specification for a detailed content model (including syntax, semantics, and behavioral models) for a given business use case.

+

hData is designed for ease of implementation and improved efficiency by reducing the size of the data set, implementing a single way to represent data, and using standard web best practices. Crucial to achieving these design goals is a clear separation of content and exchange specifications. For this, the HL7 hData Record Format defines the concept of a hData Content Profile (HCP), which allows the specification for a detailed content model (including syntax, semantics, and behavioral models) for a given business use case.

From 6bb96c69fb29a962b4d60a9b7741a31bf7b2705c Mon Sep 17 00:00:00 2001 From: toby cabot Date: Thu, 5 Jan 2012 17:44:16 -0500 Subject: [PATCH 3/4] added protocol to the email link --- index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/index.html b/index.html index e175c71..75a6c5f 100644 --- a/index.html +++ b/index.html @@ -18,7 +18,7 @@

hData is designed for ease of implementation and improved efficiency by reducing the size of the data set, implementing a single way to represent data, and using standard web best practices. Crucial to achieving these design goals is a clear separation of content and exchange specifications. For this, the HL7 hData Record Format defines the concept of a hData Content Profile (HCP), which allows the specification for a detailed content model (including syntax, semantics, and behavioral models) for a given business use case.

- +
From 0854b5759429c18130b585b90d6d28614dc274bc Mon Sep 17 00:00:00 2001 From: toby cabot Date: Wed, 10 Oct 2012 17:14:23 -0400 Subject: [PATCH 4/4] Fix small typos and spelling errors --- faq.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/faq.html b/faq.html index 74cfb66..6d4229e 100644 --- a/faq.html +++ b/faq.html @@ -22,7 +22,7 @@
What is hData?
-

hData is a simple health IT exchange framework for the creation, storage, and exchange of health data. The core hData specifications contains two components:

+

hData is a simple health IT exchange framework for the creation, storage, and exchange of health data. The core hData specifications contain two components:

  1. HL7 hData Record Format (HRF): The HRF describes an abstract architecture of how data is stored in multiple XML documents and is organized in a hierarchy. It also contains a concrete schema for the HRF meta-data. Records conforming to the HRF are called hData Records (HDRs).
  2. OMG hData RESTful Transport (HRA): When the HRF is represented as a web resource, this RESTful specification allows for modifying section documents, creation of new data, record transport, and management of the entire record through a simple Web API.
    3. @@ -32,16 +32,16 @@
How will hData be used to exchange EHR health data?
-

At its core, hData is a simple way of organizing data into small pieces in folders, with a corresponding set of XML Schemas or other appripriate media types (such as e.g. PDFs, PNGs, or DICOM containers) to describe the small pieces. Because of this simplicity, it is easy to exchange information using hData.

-

Currently, hData has one RESTful transport binding, which is being standardized at the Object Management Group.Future transports may include SMTP or XMPP transports.

+

At its core, hData is a simple way of organizing data into small pieces in folders, with a corresponding set of XML Schemas or other appropriate media types (such as e.g. PDFs, PNGs, or DICOM containers) to describe the small pieces. Because of this simplicity, it is easy to exchange information using hData.

+

Currently, hData has one RESTful transport binding, which is being standardized at the Object Management Group. Future transports may include SMTP or XMPP transports.

What is the standardization status of hData?
-

hData has been reviewed by HL7 and OMG and is in the process of becoming a normative standarf. Please check the Standardization page for a detailed status.

+

hData has been reviewed by HL7 and OMG and is in the process of becoming a normative standard. Please check the Standardization page for a detailed status.

How does hData relate to the recently proposed Resource For Healthcare idea?
-

Resources For Healthcare (RFH) was recently (09-2011) proposed as a reponse to the HL7 Fresh Look Task Force question: "How would a complete health IT software stack look like, if HL7 re-did it today?"

+

Resources For Healthcare (RFH) was recently (09-2011) proposed as a reponse to the HL7 Fresh Look Task Force question: "What would a complete health IT software stack look like, if HL7 re-did it today?"

Conceptually, RFH is using a RESTful transport to allow the exchange of the simplified content. There is a signficant overlap with hData of the way transport within the RFH proposal is realized, so that it should be quite easy to reformulate RFH in hData terms. Based on discussions with the RFH authors, they are starting to find similar issues that drove hData development (such as metadata definition) - these problems have largely been solved within hData.

Going forward, the RFH content model can be understood as a hData Content profile. This will require some work on the OMG hData RESTful Transport, and the formulation of a comprehensive HCP covering the RFH data model.

@@ -50,7 +50,7 @@
Isn't hData all about simplified data models, XML, and that stuff?

When hData was started by MITRE, one of the guiding principles in creating hData was (and still is!) developer friendliness and simple-to-implement. Part of this approach was to create a number of HITSP C32 derived schemas covering a simple continuity of care profile. When we created these schemas (which are still available in the github repository) we understood them to be placeholders for simplified schemas and models derived from a comprehensive clinical information model through a more rigourous process.

-

With the advent of HL7 greeCDA, RFH, DCMs, and similar approaches, HL7 is now able to start developing such simplified models that can be vetted by the clinical subject matter experts.

+

With the advent of HL7 greenCDA, RFH, DCMs, and similar approaches, HL7 is now able to start developing such simplified models that can be vetted by the clinical subject matter experts.

Who is using hData?
@@ -58,7 +58,7 @@
Where will all the data models and their rendering come from?
-

hData seprates the technical framework (packaging, metadata, transport, security, etc.) strongly from the content modeling aspect of health IT. As a result, the hData specification are largely content agnostic and will rely on clinical subject matter experts and data modelers to create hData Content Profiles specifying the payload model and rendering. This can happen at a variety of places, including within the domain specific working groups with existing standards development organizations, such as HL7. In fact, this process has already started, with the Pharmacy WG at HL7 agreeing to create an hData Content Profile for a medications service. Other workgroups are expected to follow soon.

+

hData separates the technical framework (packaging, metadata, transport, security, etc.) strongly from the content modeling aspect of health IT. As a result, the hData specifications are largely content agnostic and will rely on clinical subject matter experts and data modelers to create hData Content Profiles specifying the payload model and rendering. This can happen at a variety of places, including within the domain specific working groups with existing standards development organizations, such as HL7. In fact, this process has already started, with the Pharmacy WG at HL7 agreeing to create an hData Content Profile for a medications service. Other workgroups are expected to follow soon.

Do I need to be an EHR vendor to use hData?