IHE DCC Documentation Work Group Teleconference Agenda 2016-06-07
General Business
Status Update
General Introduction
Appendices
- Appendix A - Actors
- Extract current list from Gazelle
- Mary working on.
- Extract current list from Gazelle
- Appendix B - Transaction Descriptions (new)
- Appendix C - Content Module Descriptions (new)
- May be able to pull from the Profiles wiki page
- Appendix D - Glossary
- Ready for review - waiting for review at the end of this work.
- Appendix E - Profiling
- Appendix F - Integration Statements
- Need someone with more expertise than MJ to review
- Appendix G - Namespaces (new)
- Name/Space Management
- 1. Forming a process for collecting and maintaining name spaces moving forward.
- 2. Collecting legacy data. Will move forward while working on this part.
- Subgroup should meet to define process for collecting namespaces moving forward (integrate into supplement template). Meanwhile, namespaces currently defined in various will pages will be collected into the existing Google sheet Namespace Collection Spreadsheet.
- Name/Space Management
Update: Subgroup met April 28 and came to the conclusion that instead of collecting namespaces contained on various wiki pages into a spreadsheet, the existing OID Registries wiki page will be updated to include links to each domain's wiki page where namespaces are maintained. For example
Technical Framework Volumes
The volume templates (except for Volume 4) can be updated once changes have been completed in the supplement template
- Volume 1
- Volume 2
- Volume 3
- Volume 4
- Get input from IHE USA and others (invite Laura H and Jürgen to review)
Technical Framework Supplement Template
- Should revision be more prominent (now in footer only); add to title page?
Update: Committee agreed that it should. Update has been made See template here
- Make compatible with more newer profile types
- Workflow definitions (Tone , Laura B)
- Add state transaction diagram (Vol 2)
- Aggregate Data (Vol 3)
- Generic Content Template (Laura B, Tone, Rob H); get input from Rad and ITI
Status Update: Group has been meeting. They are now reviewing each TI and FT profile to identify underlying standard. See Standards in Profiles. Next meetings 5-3, 5-17.
- The template should include instruction on how to "brand" profiles when creating multi-domain profiles. Establish a home domain for publication of the profile. The domain where it is published will have primary ownership of maintenance of the profile. Include acknowledgments section that credits the contribution of all domains involved. This will avoid having to move a supplement to another domain once published.
White Paper Template
- Review it to see if changes are necessary. Logo needs to be updated.
Utilize Tool Generated CDA Templates in Published Profiles
- Steve Moore has a pilot in process using Art Decor
- Laura Bright to work with Lisa Nelson to perform pilot with Trifolia-done
- Discussions were held during last weeks F2F. One idea was to create output from the tool in Word and publish with the IHE supplement that would contain references to the tool generated Word document.
- Mary believes there is a way to easily merge the two Word documents to avoid publishing two separate docs for each supplement and allow for internal links if desired.
Update: Lisa and Mary reviewed the process for merging two Word documents, see example here
- A bonus: it appears that once the documents are merged, references created in the IHE supplement become active links to the proper section of the merged tool generated document
- Lisa and I had some discussion about what to call the merged tool generated content, a Volume, an Appendix or something else. We came to the conclusion it should be an appendix, UV realm content would be an appendix to Volume 3, others would be an Appendix to Volume 4.
Alleviate Deprecated Docs appearing in Google Search
- Jose has a process and sample doc to show
- Jose created and demonstrated a process using a script he developed to mark "outdated" or "deprecated" on obsolete documents.
- Action: RSNA staff will discuss possibilities of doing this with current CMS with marketing/web team.
- Jose created and demonstrated a process using a script he developed to mark "outdated" or "deprecated" on obsolete documents.
Update: Access is possible, draft cover page and watermark created, Jose forwarded script. Next step: Chris and Mary run test with IHE documents
Update applicable wiki pages
New Business
- Document Repository other than FTP
- First step is to identify requirements.
- Add publishing documents in additional formats (HTML)
- Update: Word to HTML test result here
- Action: Create subgroup to further develop this and submit proposal to DCC; Nichole will send out doodle poll to find 1 hour per month
- Subgroup: Eric Heflin, Rob Horn, Jose Costa Teixiera, Daniel Berezeanu, Mary and Chris
Questions: Has this group been set up; was there any further discussion during last weeks F2F meetings?
- Ideas brought up on April 19, 2016 call to improve process for creating / updating TF documents:
- Low hanging fruit
- Make up some simple checklists to aid authors and help alleviate updating old documents:
- Writing a CP
- Creating a new supplement
- Updating an existing supplement or TF Volume
- Make the revision of the document more prominent-Done
- Make up some simple checklists to aid authors and help alleviate updating old documents:
- Longer term projects:
- To help authors find things:
- Create a landing page that leads to templates (CP, Brief Profile Proposal, Supplement, etc.)
- Create "IHE Governance" of how to create and update documents
- Document repository (something other than ftp site)
- To help authors find things:
- Low hanging fruit