-
Notifications
You must be signed in to change notification settings - Fork 1
meeting July 9 2020
JohnMoehrke edited this page Jun 17, 2022
·
1 revision
https://github.com/orgs/IHE/projects/3
Agenda proposal:
- Close Issue 7 on license recommendation https://github.com/IHE/supplement-template/issues/7
- Closed recommending we use CC-By-4.0
- ACTION @John: Create an issue to change the ig template footer to this
- ACTION @John: Add the license to supplement_template
- ACTION @John: Add instruction to guidance to IHE authors
- Close issue 3 on recommending FSH be used https://github.com/IHE/supplement-template/issues/3
- Closed endorsing recommending FSH as the default recommendation to IHE authors
- ACTION @John: change supplement_template to recommendation to use FSH
- Close Issue 1 on the raw web server https://github.com/IHE/supplement-template/issues/1 -- further refinement of the use of this is outside of issue 1.
- Closed
- Discussion Issue 4 on UML vs ExampleScenario https://github.com/IHE/supplement-template/issues/4
- Closed recommending that any UML diagram should be in PlantUML code or ExampleScenario. Thus recommending both, and recommending against UML like diagrams being done in visio, powerpoint, or other.
- Note that powerpoint is likely to still be used for non-UML like diagrams
- Discussion of latest updates to the IHE template. What is now supported that was not before (e.g. History)? What got fixed (e.g. colors and icon?)
- Committee reviewed online and only comment was the CC-By-4.0 noted above needs to be changed
- ACTION @All: Review the style layout currently recommended. This can be seen by reviewing the FormatCode IG
- http://build.fhir.org/ig/IHE/FormatCode/branches/master/index.html
- Any issues should be entered as issues against the github repo for the style template https://github.com/IHE/ihe-ig-template
- Note that the given FormatCode IG is on target to be published later this month on our formal external web site; but is not yet approved.
- Discussion of layout structure proposals
- Jose diagram of structure
- How strict do we want to be? Seems we will just be recommending, and not mandating.
- Discussion of how IG can inform connectathon
- John notes that MHD and PIXm include a TestPlan as part of the recommended template to inform the testing
- http://build.fhir.org/ig/JohnMoehrke/ITI.PIXm/branches/master/index.html
- http://build.fhir.org/ig/JohnMoehrke/MHD-fsh/branches/master/index.html
- Bill will review
Note: I have re-arranged the teams on the IHE github under the recommendation of the Devices team, who have more experience. Creating a team for this work. Let me know if you have trouble on github.