OHIE 1.0

All,

As we work through the details toward our goals for successful IHE testing and OHIE 1.0 Integration Testing, we wanted to take a moment to lift our heads and think about what completing OHIE V1.0 might look like, and the appropriate deliverables that the OHIE Community seeks to offer to the wider community.

We are well on our way to creating and completing many of these deliverables, and maintaining a comprehensive, collaboratively developed list of what is needed will help us as we work toward this goal. Below is a list of the high-level deliverables:

  • Planning and implementation guides for each architecture component.
  • 1.0 Workflows
  • The documentation of the workflow has been reviewed and links to any applicable standards.
  • The workflow is tested to ensure the interactions between components function as documented.
  • Software
  • Links to the software versions that were integration tested.
  • Links to software documentation including installation and configuration guides.
  • OHIE Demonstration Environment
  • Refreshed to utilize versions of the exemplar software that were integration tested
  • Populated with anonymized data that works together.

Please feel free to openly share your perspectives, including the accuracy and completeness of this list. We would love your thoughts and feedback.

All the best,

Shaun

···

Shaun J. Grannis, MD MS FACMI FAAFP
Biomedical Research Scientist, The Regenstrief Institute
Associate Professor, I.U. School of Medicine
410 West 10th Street, Suite 2000
Indianapolis, IN 46202
(317) 274-9092 (Office)
(317) 274-9305 (Fax)

Hi Shaun,

All of the above are cover what I was thinking for the OpenHIE 1.0 release. One other thing that may be useful is a summary of what profiles each component need to support to act as a OpenHIE compliant component (eg. an OpenHIE compliant SHR). The SHR and IL communities have started something similar to this:

Cheers,

Ryan

···

On Mon, Jan 19, 2015 at 7:29 PM, Shaun Grannis sgrannis@gmail.com wrote:

All,

As we work through the details toward our goals for successful IHE testing and OHIE 1.0 Integration Testing, we wanted to take a moment to lift our heads and think about what completing OHIE V1.0 might look like, and the appropriate deliverables that the OHIE Community seeks to offer to the wider community.

We are well on our way to creating and completing many of these deliverables, and maintaining a comprehensive, collaboratively developed list of what is needed will help us as we work toward this goal. Below is a list of the high-level deliverables:

  • Planning and implementation guides for each architecture component.
  • 1.0 Workflows
  • The documentation of the workflow has been reviewed and links to any applicable standards.
  • The workflow is tested to ensure the interactions between components function as documented.
  • Software
  • Links to the software versions that were integration tested.
  • Links to software documentation including installation and configuration guides.
  • OHIE Demonstration Environment
  • Refreshed to utilize versions of the exemplar software that were integration tested
  • Populated with anonymized data that works together.

Please feel free to openly share your perspectives, including the accuracy and completeness of this list. We would love your thoughts and feedback.

All the best,

Shaun

Shaun J. Grannis, MD MS FACMI FAAFP
Biomedical Research Scientist, The Regenstrief Institute
Associate Professor, I.U. School of Medicine
410 West 10th Street, Suite 2000
Indianapolis, IN 46202
(317) 274-9092 (Office)
(317) 274-9305 (Fax)

You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.

To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

Ryan Crichton

Lead Developer, Jembi Health Systems | SOUTH AFRICA

Mobile: +27845829934 | Skype: ryan.graham.crichton
E-mail: ryan@jembi.org