Thanks for sharing this outline.
The first section on architecture I think should be quite detailed.
A big thing I am trying to understand is permissions: permissions-to-humans vs permissions-to-systems. I am not sure how that fits in in the table of contents.
Once again, I think framing a lot of content in terms of user stories or interoperability use cases would be very helpful.
···
On 27 June 2016 at 11:06, Carl Fourie carl@jembi.org wrote:
Thanks for posting this Brian
I think it is a good way to bring in some of the questions that are floating out there and where the “what would you like to see of the OHIN wiki?” question’s answers could feed into. Alvin I agree that the framing of the audiance is important and in some internal discussions we had thought of creating “entry points” for the 3 types of users that teh OHIN is looking to support (Brian laid these out earlier). It would be great to start getting some of that content into the pages and this may actually be a good place to propose a call? to discuss this moving forward?
Thoughts from the Network?
–
You received this message because you are subscribed to the Google Groups “OpenHIE Implementers Network (OHIN)” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-implementers+unsubscribe@googlegroups.com.
To post to this group, send email to ohie-implementers@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ohie-implementers/CAFNRjWiF2a%3DzB1BiaFHGp7hXY5nubpSoeTuQEZuni_g4YCOxwQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
–
Regards
Carl Fourie
Senior Program Manager | Digital Health Division
Jembi Health Systems | SOUTH AFRICA
Mobile: +27 71 540 4477 | Office: +27 21 701 0939 | Skype: carl.fourie17
E-mail: carl.fourie@jembi.org
Email Disclaimer:
This e-mail contains proprietary and confidential information some or all of which may be legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail and then deleting same. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail. Jembi Health Systems NPO, its subsidiaries and associated companies is not liable for the security of information sent by e-mail and accepts no liability of whatsoever nature for any loss, damage or expense resulting, directly or indirectly, from the access of this e-mail or any attachments hereto.
On Mon, Jun 27, 2016 at 8:56 AM, Brian Armstrong brian.armstrong@jembi.org wrote:
Hi,
I have created a Wiki page with the OHIE Guidebook Table of Contents that was proposed at the start of this thread. Can we get the community to update this and suggest further modifications, and then we can start linking in the existing content, and produce new content to help solidify the use cases and requirements.
Thanks,
Brian
–
You received this message because you are subscribed to the Google Groups “OpenHIE Implementers Network (OHIN)” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-implementers+unsubscribe@googlegroups.com.
To post to this group, send email to ohie-implementers@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
To view this discussion on the web visit https://groups.google.com/d/msgid/ohie-implementers/CAKRUSZWZKqr_Xtp8N7cp1viWLJa2H4iTAy1RWSWoDgcy-zOwRw%40mail.gmail.com.
Regards
Brian Armstrong
Digital Health Systems Architect
Jembi Health Systems | SOUTH AFRICA
Mobile: +1-778-984-4009 | Office: +27 21 701 0939 | Skype: briankarmstrong
E-mail: brian.armstrong@jembi.org
Web: www.jembi.org
On Fri, Jun 24, 2016 at 2:16 PM, Brian Armstrong brian.armstrong@jembi.org wrote:
Hi Jamie,
I am going to put the OHIE Guidebook Table of Contents up on the Wiki. I will send a link shortly.
I don’t have access to the content at the link you shared. How do I get a copy of that resource document?
Regards
Brian Armstrong
Digital Health Systems Architect
Jembi Health Systems | SOUTH AFRICA
Mobile: +1-778-984-4009 | Office: +27 21 701 0939 | Skype: briankarmstrong
E-mail: brian.armstrong@jembi.org
Web: www.jembi.org
On Fri, Jun 24, 2016 at 10:15 AM, Thomas, Jamie jt48@regenstrief.org wrote:
Brian this is great. Do you see this as a space on the wiki that we can point people to. Also I think much of the content could come from http://store.elsevier.com/Health-Information-Exchange/isbn-9780128031353 /,
which we have access to.
**Jamie Thomas **|****Health Information Project Manager/Communications
Center for Biomedical Informatics
1101 West Tenth Street
Indianapolis, IN 46202
Tel 317-274-9218 | Fax 317-274-9305
Email: jt48@regenstrief.org | Skype: jamie.thomas5670 | Twitter: @RegenstriefGHI
www.regenstrief.org
Confidentiality Notice: The contents of this message and any files transmitted with it may contain confidential and/or privileged
information and are intended solely for the use of the named addressee(s). Additionally, the information contained herein may have been disclosed to you from medical records with confidentiality protected by federal and state laws. Federal regulations and
State laws prohibit you from making further disclosure of such information without the specific written consent of the person to whom the information pertains or as otherwise permitted by such regulations. A general authorization for the release of medical
or other information is not sufficient for this purpose.
If you have received this message in error, please notify the sender by return e-mail and delete the original message. Any retention,
disclosure, copying, distribution or use of this information by anyone other than the intended recipient is strictly prohibited.
From: ohie-implementers@googlegroups.com on behalf of “alvin.marcelo@gmail.com” alvin.marcelo@gmail.com
Reply-To: “admarcelo1@up.edu.ph” admarcelo1@up.edu.ph
Date: Friday, June 24, 2016 at 1:09 PM
To: “brian.armstrong@jembi.org” brian.armstrong@jembi.org
Cc: “OpenHIE Implementers Network (OHIN)” ohie-implementers@googlegroups.com
Subject: Re: [ohie-implementers] OHIE Guidebook Outline and Framework Recommendations
Hi Brian,
Thanks for initiating this. My suggestions:
Put the ‘Why OpenHIE’ at the first part to set the context. This could contain real work problems faced by the reader. This also levels off the audience on what problems ohie tries to solve.
Put a practical part at the end that tries to show how OpenHIE’is able to solve one of the problems mentioned in Why OpenHIE. Off the bat, one such problem might be integrating data from diverse EMRs into the SHR. Another might be transforming
the SHR into an SDG regional report.
The group might want to answer a philosophical question at the outset as this will influence the flavor of the document:
Are we presenting this to car drivers or to the mechanics? Deciding on one helps us focus on the content. We can then do the next one for the other type and maybe another for car owners…
My two cents. I would like to contribute to the part on SHR to SDG…
Alvin
Hello everyone,
I wanted to share some analysis that has been drafted into a high level outline in an attempt to synthesize the OpenHIE (“OHIE”) framework, as an OHIE Guidebook. Within the list below you will see a suggested list of categories and concepts
for the OHIE Guidebook, which we are proposing for discussion within the OHIE Community.
Can I ask for suggestions from the OHIE Community to firm up this list? I think we can start the conversation here and then open it up to the other OHIE Community lists (e.g. Architecture, Shared Health Record, Terminology Services, etc.).
I have been participating in many of the Architecture calls and Security and Privacy discussions, and have been working on redrafting a requirements framework for the Shared Health Record. I would personally be interested in discussing further these elements,
but any and all categories of OpenHIE is of interest.
I look forward to further discussions.
Thanks,
Brian
Regards
Brian Armstrong*
Digital Health Systems Architect
Jembi Health Systems | SOUTH AFRICA
Mobile: +1-778-984-4009 | Office: +27 21 701
0939 | Skype: briankarmstrong
E-mail: brian.armstrong@jembi.org
Web: www.jembi.org
OHIE Guidebook Table of Contents (proposed)
- Introduction
- What is OpenHIE?
- The Architecture
- Design Principles
- Client Registry (CR)
- Facilities Registry (FR)
- Health Worker / Provider Registry (HWR / PR)
- Shared Health Record (SHR)
- Terminology Service (TS)
- Interoperability Layer
- Standards (existing standards and future standards in OHIE)
- The Tools (e.g. MIRTH Connect, OpenHIM, etc.)
- The Community
- General
- Regional Forums
- National Forums
- Client Registry Community
- Facilities Registry Community
- Health Management Information Systems Community
- Health Worker Registry Community
- Interoperability Layer Community
- PEPFAR Data Exchange Community
- Shared Health Record Community
- Terminology Services Community
- What it’s NOT
- Not an EHR
- Not a Laboratory Information System
- Not a Pharmacy Information System
- Not a…more ideas?
- Getting Engaged
- Why OpenHIE?
- The Business Problem
- The Data Problem
- The Technology Problem
- The Interop Problem
- Designing based on OpenHIE
- A fit for purpose architecture
- Implementation / architecture pattern (something like this)
- How to Implement OpenHIE
- Minimum requirements
- Mine existing Implementation Guides
- Implementation patterns
- Rapid HIE Solution - “I need to implement HIE end-to-end but I only have 40 hours, what can I accomplish?”
- HIE-in-a-Box / Turnkey / Sandbox Solutions
- Virtual machines representing the core components of HIE pre-configured to be accessible out of the box. Using open source systems (e.g. OpenMRS, OpenHIM, OpenLIMS, OpenLMIS, MIRTH Connect, DHIS2, etc.)
- Use environments: Dev / Test / Training / Conferences
- Enterprise Solutions
- Microsoft Windows based platforms
- Not-necessarily-open-source
- MSSQL and Oracle-based SQL servers
- Commercial HL7 / FHIR tools
- Commercial EHRs
- HIE Capability Model (reduced or expanded based upon requirements)
- Core Functional Capabilities
- Clinical Enabling Capabilities
- Technical Enabling Capabilities
- Minimum Enabling Capabilities
- OpenHIE and Health Systems Mapping
- Potentially a foundation model of OpenHIE systems / components and which open source systems implement the OpenHIE architecture (i.e. Facilities Registry can be located in DHIS2).
- Designs of OpenHIE and mapping of systems for each particular country.
- Interface development
- Messaging framework (e.g. HL7, FHIR, etc.)
- Governance
- Privacy
- Security
- Owners / Sponsors
- eHealth Framework
- Regulatory Framework
- Systems Framework
- Data Standards
- Maintenance and Lifecycle Management
- Software Updates
- Hardware Upgrades and Maintenance
- Deprecation
- Licensing (in the case of Enterprise Solutions)
- Networks & Connectivity
- Satellite
- WiFi
- Cellular Data (e.g. 3G, LTE, etc.)
- Shared Networks
- Partner Networks
- Community Networks
- ‘Sneaker-Net’
- Resources
- Consulting Services
- Logistics Management Services
- Program Development Services
- Software and Program Development Services
- Support
- IT Support
- Contact Centre and Help Desk
- Document Management (e.g. Architecture and PMO Repositories, CMDB)
- Knowledge Management (e.g. Case Studies, Clinical guidelines, Use Cases, Workflows, etc.)
- Training
- Certifications / Qualifications (i.e. lists and purpose)
- Curriculum development
- Offline / Online Training
- Workshops
- Train-the-Trainer
- Case Studies (Existing Implementations)
- Implementer Documented Implementations
- RHIE
- Etc
- Glossary of terms
…
–
You received this message because you are subscribed to the Google Groups “OpenHIE Implementers Network (OHIN)” group.
To unsubscribe from this group and stop receiving emails from it, send an email to
ohie-implementers+unsubscribe@googlegroups.com.
To post to this group, send email to
ohie-implementers@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/ohie-implementers/CAEHg8%2BJg%2BJRo5KK4fhFNSWmNc8pn4SJ5Sv3%3DVRLv_iyS6PpXkA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Elaine Baker
+255715568512
![F447BFA7-64CF-416E-9382-5383D9F359EA[15].png](https://discourse.ohie.org/uploads/default/original/1X/921ca8b7deaf8e796929e5a31a55a752f0687197.png){kind=small}
