ihe / hie-whitepaper Goto Github PK

Given that the HIE-Whitepaper will be published for public comment at the same times as the html version of the Technical Framework; AND given that html version of the Technical Framework includes Volume 1 chapters for all profiles (final text and trial implementation);

When we mention a profile, link to the html page for that profile

So That a reader can quickly go deeper into the profile text.

with pro and con of each
This might be an independent whitepaper?

Include description of how content can be consumed in using QEDm by way of mXDE decomposing documents

at the bottom of the document is a link to github issues for tracking comments. Add to this the use of the classic IHE form. Duplicate the recommendation at the top of the paper as well as at the bottom.
(Note elsewhere discussion of template)

GitHub enables us to use theme for these projects. The theme mechanics they support is documented here
https://help.github.com/en/github/working-with-github-pages/adding-a-theme-to-your-github-pages-site-with-the-theme-chooser

I think we should first look at the pre-canned theme choices. I like minimal. We can always change that decision later, but it seems we need to chose something. I see jekyll mentioned, which I understand is an html rendering engine, and one the HL7 IG publisher uses... so future we might be able to get creative.

Publications workgroup is looking at the alternatives. HIE-Whitepaper will be a good experiment.

Discussion in other IHE forums indicate that CC-BY-SA-4.0 is more appropriate for IHE works.

Should XCPD variations be discussed? record location, cross-reference, demographics, etc.

Ask of @jlamy to review and offer insights on XCPD variations that should be highlighted. This is not a technical text, recommended text should be appropriate and lead the reader to the Profile for further detail and technical specifications

https://www.himss.org/resources/interoperability-healthcare

Need a paragraph and links to case-study papers on Netherlands use of Document Sharing

possibly leveraging this case study on covid-19? https://www.ihe.net/wp-content/uploads/2020/04/Netherlands_COVID-case-study_edits_4.24.20.pdf

Likely new section or sub-section on section 2.5
Point at wiki pages for content profiles (CDA, XDW, and FHIR-Document)
Start with Last paragraph in section 2.5
Add XDS-I

Given that this is a whitepaper, it does not need to go to a public comment. We have not had much success at getting comments on whitepapers. So, recommend we choose to simply publish it, with the given statements already in the text about how to submit issues.

section 7.1.6 is placed to hold a quick introduction to the Swiss use of Document Sharing. There is a link to a page, but no introduction text. Also what would be the best link or set of links?

Might need to manually number headers and TOC

likely needs adjustments

test the use of markdown tables

Add text as needed. Still need to be abstract.
Possibly section 2.5

currently shows XDW, XDR, XDS, and XCA. Need to add in MHDS.
May want to break into three pictures. First is basic PUSH, second is publish/discover, third is profile specific?

I have added the actor/transaction diagram for PMIR. This however is not the right level of detail for the whitepaper. Need a cartoon style figure that shows the flow, rather than a focus only on actors and transactions.

The section we have is just blah blah blah. infoway.

https://ihe.github.io/HIE-Whitepaper/#714-canada-infoway

Without better introduction text we should remove this section.

@djritz will check

I’ll reach out to my Infoway colleagues and see what might be right thing to include. We’re using IHE for imaging across the whole country and there have been “benefits analyses” published regarding that. I’ll see if one of those reports might be a nice thing to reference…
.

XCPD is used on the XCA backbone, but Document Source or Document Consumer would use PDQm or PDQ to do searches. (little PIX too)

DSUB has changed in the last 8 years, so this text might need updating.

Ask to @mzanardini that the text be reviewed and any alternations be recommended. This recommendation can be via email, updating this issue, or pull-request

Possibly abstract up a level as there might be too detailed content

Add a table to help reader understand the choices. place at bottom of patient manager section, prior to profile details.

• Preconditions that would lead you to chose one solution
• Constraints
• Benefits
• Drawbacks

Start with PDQ, PIX, XCPD, then PMIR

e.g.
use this profile if and only if you have the following setting
do not use this profile if you have this need

sent 7/9/2020

Hi DCC members,

IHE requests you provide links to any whitepapers or presentations that outline use of the Document Sharing (XDS, XCA, MHD, etc). Send them directly to me - [email protected]

-----background for this ask -----

The ITI committee is revising our white paper on Document Sharing (XD*) using IHE Profiles. The ITI committee would like to add a new section to this white paper that includes URL links to various whitepapers or presentations that highlight the regional deployment.

We would be happy if you created a new case-study, but are expecting that there are sufficient documents already published on the internet that we could just gather and point at. So we do not expect you to write something new.

See our working draft https://ihe.github.io/HIE-Whitepaper/ This draft is not for public consumption. We expect to have this updated by fall of this year. The formal paper is available from 2012 at
Health Information Exchange: Enabling Document Sharing Using IHE Profiles

Note we are also interested in any recommendations for improving the paper. You can share them directly with me. We are doing more than adding the case-studies section including updating to include new profiles since 2012 such as MHD. We welcome participation on this github managed project.

http://www.plantuml.com/plantuml/uml/NOyn3i8m34LtdmA9MxHB4HrOc3h02iMYbjeas0uIaWzFGcY7R3_ny_jo9tfZZSiCTZxrky577j7WzmjDYFUPP6h1zWUdz8fucKZHhlrWq306BwIUFsr-F4aqHr4VeEYEtabSa3TXCcHa4wmx5PqcoeHlB6ZLLSDZYV_c3jqZtVC5

FHIR document is a flat set of resources. Import into a system is implied as merging the resources into that system (Create/Update). Meaning that once digested it is available as FHIR resources. May still need the FHIR Document need to be persisted as Binary.

Note this is not unlike mXDE / QEDm mechanics defined for CDA-> FHIR service

these are more driven by tooling, where a reference FHIR Server comes instrumented for treating an import of a FHIR Document as a request to import the resources.

is sending a FHIR Document so easy to import that a sender should expect it will be imported?

add text to Distinction between Documents and Messages

github rendering the readme as the repo, so renaming the HIE-Whitepaper.md to readme.md will allow viewing the whitepaper at https://ihe.github.io/HIE-Whitepaper/

We can always rename again later if this doesn't work well.

provide links to some HIE case studies known to Sequoia Project

This section would indicate that it is a listing of various case-studies offered as examples of use of Document Sharing. These case-studies are not authored by IHE.

The public comment process should be defined and documented.

Using the github issue mechanism to drive similar input for any public comment.
Define consistent with the IHE public comment form https://www.ihe.net/ITI_Public_Comments/

from presentation that shows XDS, XCA, MHDS, and leverages MHD as an API to any

There are some broken links. See example below. I think a # is needed in front of the section that link is pointing to (e.g., principles-of-health-document-sharing)

3.2.3 Governance

As described in Principles of Health Document Sharing is document content neutral; uses document metadata that are represented in a structured, standard format; and supports longevity of document storage.

MHDS 50.7 started as the content of this whitepaper (shifted up a header level). Thus the text that is there has been improved in ways that likely should also be improved in the whitepaper.

• RMU and MU
• XDW and XDW-for-XCA
• APPC
• SeR
• AS4
• Async soap
• DSG
• DEN

note some of these may get addressed sufficiently in other sections. Don;t duplicate mention

Adam and Amit will gather all the caseStudies that are Document Sharing relevant for inclusion in our HIE-Whitepaper, and will evaluate them to find the most compelling 4-6 that we can highlight.

IHE currently has https://www.ihe.net/resources/user_success_stories/