This wiki has undergone a migration to Confluence found Here
Difference between revisions of "FHIR Connectathons"
Jump to navigation
Jump to search
m |
|||
| Line 15: | Line 15: | ||
*prepare a report on lessons learned or feedback. | *prepare a report on lessons learned or feedback. | ||
**Comments from experience will be DSTU comments. | **Comments from experience will be DSTU comments. | ||
| + | |||
| + | General principles of Connectathons at the IHE Wiki at http://wiki.ihe.net/index.php?title=Connectathon_Principle. | ||
[[Category:FHIR Discussion]] | [[Category:FHIR Discussion]] | ||
[[Category:FHIR Connectathons]] | [[Category:FHIR Connectathons]] | ||
Revision as of 18:14, 4 December 2013
Principles discussed in approving Connectathons associated with HL7 OOC Meetings -
- needs to be sponsored by HL7 International or an affiliate, and approved by FMG.
Criteria for FMG approval
- Must submit names of the coordinator and technical lead for the connectathon
- need to have at least one person familiar with FHIR
- Persons should have participated in a prior connectathon, having an implementation, etc…
- Remains a judgment call from FMG for now
- Identify what version of the spec on which they will draw,
- need to assert if they have requirements for a frozen version of the spec and what other requirements they have.
- describe the scenarios to execute, and
- prepare a report on lessons learned or feedback.
- Comments from experience will be DSTU comments.
General principles of Connectathons at the IHE Wiki at http://wiki.ihe.net/index.php?title=Connectathon_Principle.
