Card Tech Minutes 2017.04.05: Difference between revisions
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
:'''Technical Committee Introductions''' | :'''Technical Committee Introductions''' | ||
:Text | :Text | ||
:''' | :'''Combination of Profiles''' | ||
: | :*Values sets based on procedure. This means that we can use the same template, but use the different value sets. This format has been used in other domains. There are pros and cons to using different reports with the same templates. The option list could become quite long, which will also be difficult to reach final text, if no users test the specific modalities. Even though each template has the same goal of collecting the data and using the data will have similar end points. | ||
:*Antje reviewed the CRC Vol 1 document. In the past you had one template, which applied to content module, which applied to one report. The trick is adding the complexity of header and body constraints which can map to the profile. | |||
: | |||
Revision as of 09:26, 5 April 2017
Attendees
- Nick Gawrit, heartbase, Co-chair
- Paul Dow, ACC, Secretary
- Dan Murphy, Epic
Minutes
- Technical Committee Introductions
- Text
- Combination of Profiles
- Values sets based on procedure. This means that we can use the same template, but use the different value sets. This format has been used in other domains. There are pros and cons to using different reports with the same templates. The option list could become quite long, which will also be difficult to reach final text, if no users test the specific modalities. Even though each template has the same goal of collecting the data and using the data will have similar end points.
- Antje reviewed the CRC Vol 1 document. In the past you had one template, which applied to content module, which applied to one report. The trick is adding the complexity of header and body constraints which can map to the profile.