Card Tech Minutes 2017.04.05: Difference between revisions
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
:*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. | :*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. | :*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. | ||
==Next Steps== | |||
Antje will review the Vol. 1 document in preparation for the Face to Face meeting. The question is where do we branch the document for the various procedures. the Value set? How do we handle concepts with the different document types. We've tried to keep the use cases generic. We may need to work on the concept section as well. | Antje will review the Vol. 1 document in preparation for the Face to Face meeting. The question is where do we branch the document for the various procedures. the Value set? How do we handle concepts with the different document types. We've tried to keep the use cases generic. We may need to work on the concept section as well. | ||
Revision as of 09:43, 5 April 2017
Attendees
- Nick Gawrit, heartbase, Co-chair
- Paul Dow, ACC, Secretary
- Dan Murphy, Epic
- Rebecca Baker, ACC
- Antje Scroeder, Healthineers
- Charles Thomas, University of Washington
- Adam Hooker, Fuji Medical Systems
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.
Next Steps
Antje will review the Vol. 1 document in preparation for the Face to Face meeting. The question is where do we branch the document for the various procedures. the Value set? How do we handle concepts with the different document types. We've tried to keep the use cases generic. We may need to work on the concept section as well.