PASMinutes2012_2_21

include component="page" wikiName="siframework" page="LCC Header"

**Meeting Agenda:**

 * = **ID** ||= **Key Discussion Items** ||= **Duration** ||= **Presenter** ||
 * = 1 ||= Presentation on C-CDA Project Scope Statement Presented to HL7 Structured Documents WG ||= 25-30 minutes ||= Brett Marquard ||
 * = 2 ||= Finish Review of MDS Changes for April ||= 25- 30 minutes ||= Sue Mitchell ||
 * 4 || Next Steps || 5 minutes || Sue Mitchell ||
 * < **Geisinger Questions on MDS - CCD Conversions** ||
 * < **#** || **Item** || **Issue** ||
 * 1 || A1000A-A1000F |||||||| It wasn’t spelled out in the Rosetta stone, but digging into it it looks like these values should be coded (CDC Code System 2.16.840.1.113883.6.238 ) as defined below:

CDC Race and Ethnicity Code Set, value set OID 2.16.840.1.113883.1.11.15836 CodeSystem OID 2.16.840.1.113883.6.238 **MDSv3 question, Display Name, CDC Ethnicity Code:** 1. A1000A, American Indian or Alaska Native, 1002-5 2. A1000B, Asian, 2028-9 3. A1000C, Black or African America, 2054-5 4. A1000D, Hispanic or Lation, 2135-2 5. A1000E, Native Hawaiian/Pacific Islander, 2076-8 6. A1000F, White, 2106-3 || Error: HITSP/C83 Information Source, Author Name is a required, non-repeating data element. See HITSP/C83 Table 2-14, Data Element 10.02. <span style="color: #2a2a2a; font-family: Arial,Helvetica,sans-serif;">Location: /ClinicalDocument[1]/author[1] <span style="color: #2a2a2a; font-family: Arial,Helvetica,sans-serif;">Test: count(cda:assignedAuthor/cda:assignedPerson/cda:name) = 1 || <span style="color: #2a2a2a; font-family: Arial,Helvetica,sans-serif;">Location: /ClinicalDocument[1]/component[1]/structuredBody[1]/component[1]/section[1]/entry[1]/encounter[1] <span style="color: #2a2a2a; font-family: Arial,Helvetica,sans-serif;">Test: cda:text/cda:reference ||
 * < <span style="font-family: Arial,Helvetica,sans-serif;">2 || <span style="font-family: Arial,Helvetica,sans-serif;">C0500 || <span style="font-family: Arial,Helvetica,sans-serif;">Is it ok just to display the summary score with no other context? For example, the display would be something like:MDS C0500 (BIMS res interview: summary score): 15 ||
 * < <span style="font-family: Arial,Helvetica,sans-serif;">3 || <span style="font-family: Arial,Helvetica,sans-serif;">Items I0100 to I6500 || <span style="font-family: Arial,Helvetica,sans-serif;">Column J of “MDS Summary - Model of Use” tab does not mark these as being able to be omitted if response is “0”. Is this the intended behavior? Meaning, is there value displaying these when the answer is “0”. ||
 * < <span style="font-family: Arial,Helvetica,sans-serif;">4 || <span style="font-family: Arial,Helvetica,sans-serif;">LOINC answer sets || <span style="font-family: Arial,Helvetica,sans-serif;">One example: OID of 1.3.6.1.4.1.12009.10.1.62 – where can I find the definition of/more information for the codes within that code system? I see them defined in the MDS vocabulary XML file that came with the DSTU “CDAR2_QA_DSTUR2_201020100421”, but where can I find more information about those codes? ||
 * < <span style="font-family: Arial,Helvetica,sans-serif;">5 || <span style="font-family: Arial,Helvetica,sans-serif;">Author Name || <span style="font-family: Arial,Helvetica,sans-serif;">** How should we proceed with Author Name? Rosetta stone notes it as an issue. Should I just use MJM (facility) as the author? The HITSP schematron validator is throwing an error. **
 * < <span style="font-family: Arial,Helvetica,sans-serif;">6 || <span style="font-family: Arial,Helvetica,sans-serif;">Patient Identifier(s) || <span style="font-family: Arial,Helvetica,sans-serif;">** It looks like you can only have one ID for a patient. Should we only include the patient’s MRN from the facility? Should we not include SSNum? and other IDs? ** <span style="color: #2a2a2a; font-family: arial,helvetica,sans-serif;">Error: HITSP/C83 Personal Information -- Patient Information Entry shall contain a single non-repeating Person ID. See Table 2-5, Data Element 1.02. ||
 * < <span style="font-family: Arial,Helvetica,sans-serif;">7 || <span style="font-family: Arial,Helvetica,sans-serif;">Encounters Section || <span style="font-family: Arial,Helvetica,sans-serif;">** In the encounters sections, what should be the reference for the text element as defined in the schematron assertion below? ** <span style="color: #2a2a2a; font-family: arial,helvetica,sans-serif;">Error: In IHE PCC Encounters (1.3.6.1.4.1.19376.1.5.3.1.4.14), the text element shall contain a reference to the narrative text describing the encounter.

Attendance
Sue Mitchell, Brett Marquard, Meredith Lewis, Gay Dolan, Jennie Harvell, Leigh Ann Campbell, Susan Campbell, Terri Peterson, Teresa Mota, Zabrina Gonzaga, Shalina Wadhwani, Maureen Boyle, Rhonda York, Emma Jones

Meeting Notes
__Presentation on C-CDA Project Scope Statement Presented to HL7 Structured Documents WG (Brett Marquard)__ __Finish Review of MDS Changes for April 2012__
 * Consolidated CDA templates – completed in 2011; industry groups worked to reconcile 9 different document types into a single guide
 * Headers for different types to help explain the guide; document level template (section 3) shows document type, required sections and optional sections (with hyperlinks)
 * <span style="color: #000000; font-family: Arial,Helvetica,sans-serif;">Brett presented an overview of the HL7 scope of work to address gaps in the C-CDA, including functional status (see his PPT under SWG references). He presented two slides identifying the use of LOINC and SNOMED for assessments questions and answers, including Qs and As that focus on functional status.
 * <span style="font-family: Arial,Helvetica,sans-serif;"> Brett briefly alluded to work that Lantana is undertaking to identify and model patterns to represent Qs/As related to functional status in the C-CDA. He indicated that these patterns would be presented to the S&I PAS SWG on 2/28 ( 30-45 minutes next week to talk through modeling; discuss questions).
 * Original group felt that moving summary data forward required skin information including pressure sensitivity and ulcers – group decided this is false and it is not necessary
 * Skin tears and moisture associated skin damage – should be moved forward
 * Make sure that everyone is in agreement that the discussed items would like to be picked up; including dates (start and end time, if possible, then date/day)
 * May question recreational therapy moving forward regarding hospice patients
 * Therapy resumed and therapy resumption date – unnecessary, covered in start and end dates
 * Section Q Questions from Leigh Ann – Changes to the wording of responses to questions; did a family member or guardian participate in filling out an MDS
 * Would be interested in 100 A, B and C to determine patient involvement
 * At the end next week need to discuss the fact that this is a summary – don’t want to overwhelm the recipients; perhaps give to two or three different doctors to discuss
 * Document will be available on HIE – for anyone using this; feedback information from customers
 * Leigh Ann sees this as a phased approach – test out and then solicit opinions from those using it
 * Discharge plans -Q0400 and Q0600, would help lead to follow up if necessary (Do not need others)

Return to PAS SWG wiki page

include component="page" wikiName="siframework" page="space.template.inc_contentleft_end"