Baltimore F2F meeting

Minutes of the Weekly PGHD Meeting for 09/11/2012

Attendees:

Participant / Company / Present
Virinder Batra / IntuitHealth / X
Lisa Nelson / Life Over Time Solutions LLC / X
Elaine Ayres / National Institutes of Health
Cathy Welsh / St JudesHospital / X
Bob Dolin / Lantana Consulting / X
Emma Jones / Allscripts
Shawn Meyers / Healthwise / X
Brian Sheller / Healthwise / X
Chris Schultz / Chadis
Gordon Raup / Datuit / X
David Tao / Siemens
Jessi Formoe / IntuitHealth
Leslie Kelly Hall / Healthwise / X
Kevin Harbauer / Healthwise
Allen Traylor / Chadis
  1. Provided Project Status for SDWG
  2. Discussed requirements for theClinicalDocument/code in the header

Discussed various types of PGHD documents

  • Previsit Doc
  • Consent
  • Adherence
  • Experience of Care (for MU stage2-Leslie)
  • Request for revision or update
  • General – can include any section defined in C-CDA

Cathy Welsh asked if it would make sense to adjust the use cases to bring out the essence of these document types in our current set of use cases. i.e. Nutrition use case could be an example of Adherence document.

Conclusion/Action Items

  • We would focus on the General document as a “hierarchical parent” of the other more specific types of PGHD documents. Those would remain out of scope for this phase of the project.
  • We can provide guidance that a good place to start when implementing one of the general PGHD documents would be to include sections from the current CCD specification.
  • We are proposing the following LOINC code be used for the General PGHD: (see below)
  • Additional work on Use Cases can be done at member’s discretion, but it is not necessary to meet goals for defining the header of the PGHD General Document.
  • We also noted that it might make sense to consider re-wording the “boundary language” for the scope of C-CDA to include non-clinician generated notes. Right now the wording only includes Clinical Notes, which would exclude PGHD Documents. Preferred wording might be: …clinician generated and non-clinician generated notes…for primary care…

Can we make a detailed description to go with this?

DEFINITION/DESCRIPTION
Source:Regenstrief LOINC
Suggest a definition for this code?????

DEFINITION/DESCRIPTION
Source:Regenstrief LOINC
This document is a concise clinical document that provides an electronic, pre-defined patient health data set applicable both for unexpected, as well as expected (planned), health care contact. This document may be either the product of a medical act or an automatic excerpt from national/regional EHRs.
A Patient Summary gives a healthcare provider the essential information needed for health care coordination and, in cases of an unexpected need or when the patient consults a provider other than his regular contact person (e.g. the general practitioner he/she is registered with), this document enables continuity of care.
Because it is meant to be a summary, this document might not include a detailed medical history, details on clinical conditions or a full list of all prescriptions and dispensed medicines.