Welcome! Pediatric Data Standards SIG Meeting Q1 Working Webcast: Pediatric Specialty Profile May 5, 2008 Dial In: (866) code:

Q1: Pediatric Specialty Profile 9:00-10:30 AM Central Introductions Ground Rules Agenda and Objectives Approval of January 2008 Minutes Child Health-FP Update Derived Profiles Overview Proposed Project: Pediatric Specialty Profile Agenda

1. Use mute feature on phone 2. Avoid hold; Hang up if necessary 3. Introduce self when speaking 4. Stay on schedule 5. Stay on topic; Use parking lot 6. Expect to contribute 7. Silence is agreement 8. Be constructive Ground Rules

Meeting Objectives Q1: Pediatric Specialty Profile Approve January 2008 minutes Agree upon general direction regarding profile development Obtain enough feedback to write draft of project scope statement, if applicable

January 2008 Minutes Approval Please see handout of meeting minutes

Balloting the Child Health Functional Profile for EHR Systems

Balloting the Child Health-FP Complete intent to ballot form by October 15 Inform EHR TC (and Patient Care) of intention and seek approval Submit documentation to EHR TC and publications workgroup to create ballot documents Publicize ballot opportunity Ballot – November/December 2007 Recruit reconciliation volunteers January Work Group reconciliation session EHR TC accepts reconciliation document; N/A Second ballot period April 2008 May Work Group reconciliation session Negative voters and EHR TC accept disposition report - July 2008 Ballot – August/September 2008 *Opportunity to become HL7 ANSI standard Sept 2008 *May happen as soon as negative votes are retracted/withdrawn

Balloting the Child Health-FP Normative Process December Committee Ballot: Review a.EHR TC and PeDSSIG voted b.Required 60% return from ballot pool c.Required 2/3 affirmative votes d.22 in ballot pool; 11 affirmative, 9 abstain, 2 no vote e.90.91% approval f.If substantive changes, ballot pool will review major changes before moving to membership ballot g.No substantive changes; Moves to membership ballot

Balloting the Child Health-FP Normative Process April Membership Ballot: Review a.Open to HL7 membership for voting b.Required 60% return from ballot pool c.Requires 90% affirmative votes d.101 in ballot pool; 48 affirmative, 19 negative, 7 abstain, 7 no vote e.Needed 51 affirmatives for 90% approval; Had 48 f.Perform reconciliation work

Exploring a Child Health Specialty Derived Functional Profile for EHR Systems

Our Criteria Conformance for Derived Profile Quoted from Child Health Functional Profile for EHR Systems The Child Health-FP workgroup recognizes that developers, users, and other members of the pediatric community may wish to develop their own profiles. The workgroup contends that the Child Health-FP includes all the general functions that might be reasonably expected to be available in an EHR system used to care for children in the United States. However, we also recognize the value in the development of derived profiles applicable to certain subsets of EHR systems used to care of children. In fact, the workgroup strongly feels that the development of derived profiles will likely be essential to support the evaluation of systems designed to support subsets of child healthcare functions. For example, derived profiles for pediatric specialties, such as neonatology, could be developed to support certification in those niches. In order for a derived profile to claim conformance with the Child Health-FP, the profile SHALL include all of the Child Health-FP functions. The workgroup solicits feedback regarding functions encountered in the development of a derived profile not encountered in the Child Health-FP.

Manage Immunization Administration Statement: Capture and maintain discrete data concerning immunizations given to a patient including date administered, type, manufacturer, lot number, and any allergic or adverse reactions. Facilitate the interaction with an immunization registry to allow maintenance of a patients immunization history. Description: During an encounter, recommendations based on accepted immunization schedules are presented to the provider. Allergen and adverse reaction histories are checked prior to giving the immunization. If an immunization is administered, discrete data elements associated with the immunization including date, type, manufacturer and lot number are recorded. Any new adverse or allergic reactions are noted. If required, a report is made to the public health immunization registry. 1. The system SHALL provide the ability to recommend required immunizations, and when they are due, during an encounter based on widely accepted immunization schedules. 2. The system SHALL provide the ability to recommend required immunizations based on patient risk factors. 3. The system SHALL perform checking for potential adverse or allergic reactions for all immunizations when they are about to be given. 4. The system SHALL provide the ability to capture immunization administration details, including date, type, lot number and manufacturer. 5. The system SHALL provide the ability to capture other clinical data pertinent to the immunization administration (e.g. vital signs, adverse reactions). 6. The system SHALL record as discrete data elements data associated with any immunization. 7. The system SHOULD provide the ability to associate standard codes with discrete data elements associated with an immunization. 8. The system SHALL provide the ability to update the immunization schedule. Manage Immunization Administration Capture and maintain discrete data concerning immunizations… PeDSSIG edits in RED for CH Profile Function requested by PeDSSIG for original model now standard Example Edits and Additions to EHR FM

Sample Project Scope Decisions (see draft scope statement) 1.Name Child Health Specialties Functional Derived Profile for EHR Systems Child Health Specialties - FDP 2.Purpose 3.Scope, e.g. United States Inpatient and Outpatient Age range (0-18) Receiving care in which settings Etc. 4.Major Categories of Functions Addressed Cancer, Transplant, AIDS, Paralysis, Neonatology Intensive Care, Cardiac Intensive Care, Opthamology, Pregnancy Under Age 18, etc.

Possible Publishing Timeline Working Toward Jan 09 Ballot Cycle a.May 18: Define project scope b.May 18-Sept. 16: Project work Recruit volunteers Education session for volunteers Volunteers write first draft c.Sept 16: Review first draft of content at WGM d.Sept. 28: Revised project scope due e.Oct. 26: Intent to ballot due f.Nov. 23: Content due to HL7 for ballot

Next Meeting: Tuesday, September 16, 2008 Vancouver, BC, Canada

Monthly Calls 2008 Second Week of Each Month: Rotating Tues/Thurs (866) code: Thursday, May 8, 1-2 PM Central Tuesday, June 10, 9-10 AM Central Thursday, July 10, 1-2 PM Central Tuesday, August 12, 9-10 AM Central Thursday, September 11, 1-2 PM Central Tuesday, October 14, 9-10 AM Central Thursday, November 13, 1-2 PM Central Tuesday, December 9, 9-10 AM Central

May 8 Call Agenda Updates Immunization Project…………………………Rob Savage Quality Reporting Project……………………Pele Yu Terminology Project…………………………..Gerry Wade Profiles: Quality, Vital Stats, PHR……….Andy Spooner Highlights from May 5 Meeting…………..Andy Spooner

Thank You!

Welcome! Pediatric Data Standards SIG Meeting Q2 Working Webcast: Ballot Reconciliation May 5, 2008 Dial In: (866) code:

Q2: Ballot Reconciliation Session 11:00 AM – 12:30 PM Central Introductions Ground Rules Agenda and Objectives Child Health-FP Ballot Review Discussion and Reconciliation Voting Q3 and Q4: Canceled Agenda

1. Use mute feature on phone 2. Avoid hold; Hang up if necessary 3. Introduce self when speaking 4. Stay on schedule 5. Stay on topic; Use parking lot 6. Expect to contribute 7. Silence is agreement 8. Be constructive Ground Rules

Meeting Objectives Q2: Ballot Reconciliation Complete ballot disposition report Consensus decision making if possible

1. Address 100% of comments 2. Assign disposition to each comment Comment Responsible person Vote results (if necessary) Change applied Substantive change? 3. Vote to approve disposition recommendations Expectations

Applicable to All Comments 1. Persuasive 2. Persuasive with modification 3. Not persuasive 4. Not related 5. Referred and tracked 6. Pending input from submitter 7. Pending decision from other committee Applicable only to Affirmative Comments 1. Considered for future use 2. Considered – question answered 3. Considered – no action required Disposition Options

Materially affect intent or content of standard as balloted. Substantive Changes

Thank You!