New version of the hData specifications

3 views

Skip to first unread message

Beuchelt, Gerald

unread,

Nov 10, 2009, 11:43:45 AM11/10/09

to hdata-...@googlegroups.com, l32-g...@googlegroups.com, project-hdata...@googlegroups.com

Please find a new release of the hData specifications at the Project hData website at http://www.projecthdata.org/documents.html.

Changes:

· Added DocumentMetaData to the hData Record Format. Each SectionDocument is now associated with a meta data construct that describes some basic attributes, such as media type, hData content type (typeId), pedigree information, linked documents, etc. The schema for the meta data is included, but not complete: we are still looking at extensions for sensitivity, access control, and consent.

· Updated the hData Packaging and Network Transport Specification to support the meta data.

Please send us your suggestions and comments on these specs. Expect the Java code base to get updated in the next few days to reflect the updated specifications.

At this time, the core specs should be in reasonable shape feature-wise, and we will start to work on the content profiles: the next specification will document the requirements for an hData content profile, and from there we will release some of our schemas as “content profile building blocks”, e.g. specifications for medications, allergies, etc. to build more comprehensive content profiles from.

At the same time, we will be creating a short paper describing the security and identity management requirements and proposed solution soon.

For the hData team,

Gerald Beuchelt

Beuchelt, Gerald

unread,

Nov 12, 2009, 10:14:18 AM11/12/09

to hdata-...@googlegroups.com, l32-g...@googlegroups.com, drja...@cox.net

Jack -

Thank you very much for your email.

The idea behind L32 is to make available to a large audience as fast as possible. The schema constructs have been published at

http://github.com/projecthdata/L32

and are licensed under the Apache 2.0 license. As indicated, we are currently discussing the submission to the correct SDO, and will post once they are submitted. Note that L32 will produce C32 compliant documents, so - in a sense - they are already ratified by HITSP.

As to your question on hData's participation in NHIN: we are not (yet) participating, but one of the next steps will be to add hData interfaces to the NHIN Connect source base and publish the code.

V/r

Gerald Beuchelt

>-----Original Message-----
>From: hdata-...@googlegroups.com [mailto:hdata-
>gen...@googlegroups.com] On Behalf Of Jack Taylor InforMD
>Sent: Wednesday, November 11, 2009 10:31 AM
>To: hdata-general
>Cc: drja...@cox.net
>Subject: Re: New version of the hData specifications
>
>
>Gerald, rainy day and literally stumbled on your hData site. mini-
>background: Retired USN Surgeon, clinical informaticist x 15 years,
>currently supporting VA after 11 years of DoD Military Health System.
>question 1: having read the FAQ is there progress towards establishing
>L32 with a "carefully chosen SDO" that may eventually offer the
>construct as open source?
>question 2: I assume a considerable relationship with ONC/FHA and the
>recently announced Virtual Lifetime Electronic Record (VLER) (Obama+VA
>Sec and DoD Sec April 9). Is hData "participating" directly in the
>NHIN-Connect collaboration.
>Thank you.
>Jack Taylor MD
>703-626-5182 cell
>alt email: drja...@cox.net

>
>On Nov 10, 11:43 am, "Beuchelt, Gerald" <gbeuch...@mitre.org> wrote:
>> Please find a new release of the hData specifications at the Project
>hData website athttp://www.projecthdata.org/documents.html.
>>
>> Changes:
>>

>> * Added DocumentMetaData to the hData Record Format. Each

>SectionDocument is now associated with a meta data construct that
>describes some basic attributes, such as media type, hData content type
>(typeId), pedigree information, linked documents, etc. The schema for
>the meta data is included, but not complete: we are still looking at
>extensions for sensitivity, access control, and consent.
>>