What goes in an OpenHIE release?

All,

Because our next architecture conference call is a few weeks away, we wanted to start a few conversations via email, and would very much appreciate your input.

We’d like to develop consensus on what will be included in OpenHIE releases moving forward. In addition to the recently established OpenHIE Maturity Assessment, we believe the following elements should be part of a release, and want your feedback on these items. Those items include:

Architecture diagrams

Workflow documentation

Maturity assessment

Planning and implementation guides

Reference software

So, the question to this group: do these items seem reasonable? Are we missing anything? Should we exclude something?

Thanks you for your comments and feedback.

Best,

···

Shaun J. Grannis, MD MS FACMI FAAFP
Interim Director, The Regenstrief Institute Center for Biomedical Informatics

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)

I think it would be good to be explicit about the packaging for the reference software.

Cheers,

-carl

···

Shaun J. Grannis, MD MS FACMI FAAFP
Interim Director, The Regenstrief Institute Center for Biomedical Informatics

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)

For example, with the DATIM work, we have been working on getting some integrated packaging of the components setup under Ubuntu 14.04 (LTS). It would be good to state at which stage the reference software has been packaged. Something like:
Not packaged
Packaged for stand-alone deployment
Packaged for integrated deployment with other OpenHIE components

Cheers,
-carl

···

On Nov 14, 2016, at 12:58 PM, Grannis, Shaun J <sgrannis@regenstrief.org> wrote:

Thanks Carl – can you say more about what ‘being explicit about packaging’ looks like?

Best,

Shaun

From: <ohie-architecture@googlegroups.com <mailto:ohie-architecture@googlegroups.com>> on behalf of Carl Leitner <litlfred@gmail.com <mailto:litlfred@gmail.com>>
Date: Monday, November 14, 2016 at 10:15 AM
To: Shaun Grannis <sgrannis@gmail.com <mailto:sgrannis@gmail.com>>
Cc: "ohie-architecture@googlegroups.com <mailto:ohie-architecture@googlegroups.com>" <ohie-architecture@googlegroups.com <mailto:ohie-architecture@googlegroups.com>>
Subject: Re: What goes in an OpenHIE release?

I think it would be good to be explicit about the packaging for the reference software.
Cheers,
-carl

On Nov 10, 2016, at 1:57 PM, Shaun Grannis <sgrannis@gmail.com <mailto:sgrannis@gmail.com>> wrote:

All,

Because our next architecture conference call is a few weeks away, we wanted to start a few conversations via email, and would very much appreciate your input.

We'd like to develop consensus on what will be included in OpenHIE releases moving forward. In addition to the recently established OpenHIE Maturity Assessment, we believe the following elements should be part of a release, and want your feedback on these items. Those items include:

Architecture diagrams <Log In - OpenHIE Wiki;
Workflow documentation <Log In - OpenHIE Wiki;
Maturity assessment <Log In - OpenHIE Wiki;
Planning and implementation guides <Log In - OpenHIE Wiki;
Reference software <Log In - OpenHIE Wiki;

So, the question to this group: do these items seem reasonable? Are we missing anything? Should we exclude something?

Thanks you for your comments and feedback.

Best,
----
Shaun J. Grannis, MD MS FACMI FAAFP
Interim Director, The Regenstrief Institute Center for Biomedical Informatics
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 <mailto:ohie-architecture+unsubscribe@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.

--
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 <mailto:ohie-architecture+unsubscribe@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.