This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Conference call minutes 8 December 2015"
Jump to navigation
Jump to search
Michael tan (talk | contribs) (→Topics) |
Michael tan (talk | contribs) (→Topics) |
||
| Line 36: | Line 36: | ||
* The DAM itself is agnostic of systems. Currently most enviroments can only deal with concerns within one system. | * The DAM itself is agnostic of systems. Currently most enviroments can only deal with concerns within one system. | ||
* A list is a presentation ( or appearance) of grouped information. Problem lists or allergy lists are some (of the most common examples) of output. It is not the problem concern or health concern itself. | * A list is a presentation ( or appearance) of grouped information. Problem lists or allergy lists are some (of the most common examples) of output. It is not the problem concern or health concern itself. | ||
| − | * The structure of a problem concern is identical to the health concern. A health concern could be nested and have subconcerns. That is the reason why you do not see the problem concern as a seperate data element | + | * The structure of a problem concern is identical to the health concern. A health concern could be nested and have subconcerns. That is the reason why you do not see the problem concern as a seperate data element in the diagram. |
* MU3 does need rules of how to build your sections and subsections and how to use the templates. These are guidelines of implementation, that will set restrictions to the nesting and grouping of health concerns. | * MU3 does need rules of how to build your sections and subsections and how to use the templates. These are guidelines of implementation, that will set restrictions to the nesting and grouping of health concerns. | ||
Revision as of 14:26, 9 December 2015
Health Concern Topic
Patient Care WG
December 8 2015
Attendees:
- Michael Tan – Chair
- David Pyke
- David Tao
- Jay Lyle
- Susan Matney
- Emma Jones
- Dan Russler
- Pavla Frazier
Participation Information
Phone Number: +1 770-657-9270
Participant Passcode: 943377
Web Meeting Info www.webex.com Meeting number 249 522 346
Topics
- David Pyke has sent a new DAM document to the patient care list.
- The chapters 4, 5 and 6 were thoroughly revised and shortened.
- The following actions are still outstanding:
- review the use case scenario's:
- remove redundant scenario's
- Patient journey scenario should reflect the patient's perspective.
- Better example of a storyboard with the patient's concern.
- update the comparison in the appendix between (newer versions of ) DAM, CCDA and Contsys.
- review the use case scenario's:
- Dan is anxious to know how health concerns will work from the patient's perspective.
- There are different roles attached to a health concern. The DAM does not make a distinction in the background of the author. This could be a patient.
- The DAM itself is agnostic of systems. Currently most enviroments can only deal with concerns within one system.
- A list is a presentation ( or appearance) of grouped information. Problem lists or allergy lists are some (of the most common examples) of output. It is not the problem concern or health concern itself.
- The structure of a problem concern is identical to the health concern. A health concern could be nested and have subconcerns. That is the reason why you do not see the problem concern as a seperate data element in the diagram.
- MU3 does need rules of how to build your sections and subsections and how to use the templates. These are guidelines of implementation, that will set restrictions to the nesting and grouping of health concerns.
- The document can be found here:
Action items
- Michael will send Jay's document with the aggregated comments to Dave Pyke
- David will incorporate Jay's proposal into the original DAM.
Go back to health concern minutes[[1]]
