Care Team Domain Analysis Model Version 2 PSS

1a. Project Name Care Team Domain Analysis Model Version 2 PSS 1b. Project ID 1699 1c. Is Your Project an Investigative Project (aka PSS-Lite)? No 1d. Is your Project Artifact being Reaffirmed or proceeding to Normative directly after being either Informative or STU? No 1e. Today's Date 1f. Name of standard being reaffirmed 1g. Project Artifact Information 1h. ISO/IEC Standard to Adopt 1i. Does the standard include excerpted text from one or more ISO, IEC or ISO/IEC standards, but is not an identical or modified adoption? 1j. Unit of Measure 2a. Primary/Sponsor WG Learning Health Systems 2b. Co-Sponsor WG Patient Care 2c. Co-Sponsor Level of Involvement Request formal content review prior to ballotRequest periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.) 2c. Co-Sponsor Update Periods WGMs 2b. Co-Sponsor WG 2 Public Health 2c. Co-Sponsor Level of Involvement Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.) 2c. Co-Sponsor 2 Update Periods WGMs 2b. Co-Sponsor WG 3 Clinical Information Modeling Initiative 2c. Co-Sponsor Level of Involvement Request formal content review prior to ballotRequest periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.) 2c. Co-Sponsor 3 Update Periods WGMs 2d. Project Facilitator Russell Leftwich 2e. Other Interested Parties (and roles) Dr. Stephen Chu, SME; Clinical Quality Information WG 2f. Modeling Facilitator Claude Nanjo 2g. Publishing Facilitator Dr. Russell Leftwich 2h. Vocabulary Facilitator Rob Hausam 2i. Domain Expert Representative Stephen Chu; Russell Leftwich; Claude Nanjo; Emma Jones; Chris Melo; Lindsay Hoggle; Thomson Kuhns 2j. Business Requirements Analyst Emma Jones RN -BC 2k. Conformance Facilitator 2l. Other Facilitators 2m. Implementers University of Utah 3a. Project Scope This project will construct a domain analysis model (DAM)of the patient centered care team unique for an individual including health professionals, caregivers in healthcare organizations, family members, community caregivers, clinical investigators and other individuals or organizations involved in support services. Characteristics of team members are expected to include name, professional licenses and certifications, organizational and jurisdictional IDs, contact information including electronic end-point addresses. Attributes will also include 1) each team members’ role with respect to the patient and relationships with others on the care team, 2) participation in care delivery including that of family members, 3) participation in care planning and care coordination, 4) consent authorizations, 5) health literacy and care delivery capabilities of family and community caregivers, 6) and unique skills such as language skills. The existence of appropriate value sets for attributes of team members will also be evaluated. The DAM will also address interoperability needs and opportunities between members of the care team. This includes but is not limited to: • Security and appropriate access • Role-based rights to Care Planning which include authorship, stewardship, and custodianship. • Role base privileges • Evaluate existing privacy and security framework as might be applied to care team and care plans This project will be accomplished iteratively with ongoing evaluation as care team and care coordination concepts evolved. Attachments 3b. Project Need Version one of the Care Team Domain Analysis Model (DAM) addressed the following and exposed the need to address existing privacy and security framework as might be applied to care team and care plans. The concept of a learning health system is one in which each activity in care and health promotion is informed by the collective knowledge of the system and the results of each activity update the knowledge of the system. A codified representation of the often referenced patient-centered care team and care team roster does not exist. A publicly available, comprehensive model of the characteristics and attributes of care team members, including family and community caregivers, does not exist. Neither is there a model of the relationships between various specified care team members or roles and an individual patient, which would include the participation of each care team member in delivery of care, health maintenance, care planning, and care coordination. Effective care coordination with the aims of patient engagement, optimal outcomes, accountable care, consent management, and patient safety can only be possible with a representation of the care team that captures important characteristics of team members in an interoperable way. Future versions of the Care Team DAM may be needed to address potential unforeseen gaps that may be revealed as this work evolves. Addition potential gaps may include artificial intelligence, machine learning to enable a truly learning health systems. 3c. Security Risk No 3d. External Drivers ONC - Care Team (USCDI Data Class) 3e. Objectives/Deliverables and Target Dates Comment only ballot to validate scope. September 2021 Draft document for informative ballot - January 2022 Ballot reconciliation-May 2022 Publish DAM as informative document-June 2022 Project iterative updates as needed - ongoing 3f. Common Names / Keywords / Aliases: Learning Health System, LHS, Care Team, Care Team Roster, Care Coordination 3g. Lineage 3h. Project Dependencies 3i. HL7-Managed Project Document Repository URL: https://confluence.hl7.org/display/LHS/Learning+Health+Systems 3j. Backwards Compatibility N/A 3k. Additional Backwards Compatibility Information (if applicable) 3l. Using Current V3 Data Types? N/A 3l. Reason for not using current V3 data types? 3m. External Vocabularies Unknown 3n. List of Vocabularies 3o. Earliest prior release and/or version to which the compatibility applies 4a. Products Domain Analysis Model (DAM) 4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to? 4c. FHIR Profiles Version 4d. Please define your New Product Definition 4d. Please define your New Product Family 5a. Project Intent Revise current standard 5a. White Paper Type 5a. Is the project adopting/endorsing an externally developed IG? 5a. Externally developed IG is to be (select one) 5a. Specify external organization 5a. Revising Current Standard Info update the Patient Centered Care Team DAM Release 1 with subsequent comment only and informative ballots as required to elaborate this DAM 5b. Project Ballot Type Comment (aka Comment-Only), Informative 5c. Additional Ballot Info 5d. Joint Copyright No 5e. I understand I must submit a Joint Copyright Letter of Agreement to the TSC in order for the PSS to receive TSC approval. no 6a. External Project Collaboration 6b. Content Already Developed 20% 6c. Content externally developed? No 6d. List Developers of Externally Developed Content 6e. Is this a hosted (externally funded) project? No 6f. Stakeholders Clinical and Public Health Laboratories, Immunization Registries, Quality Reporting Agencies, Regulatory Agency, Standards Development Organizations (SDOs), Payors 6f. Other Stakeholders 6g. Vendors Pharmaceutical, EHR, PHR, Equipment, Health Care IT, Clinical Decision Support Systems, Lab, HIS 6g. Other Vendors 6h. Providers Clinical and Public Health Laboratories, Emergency Services, Local and State Departments of Health, Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health) 6h. Other Providers 6i. Realm Universal 7d. US Realm Approval Date 7a. Management Group(s) to Review PSS 7b. Sponsoring WG Approval Date Mar 16, 2021 7c. Co-Sponsor Approval Date Mar 22, 2021 7c. Co-Sponsor 2 Approval Date Jul 15, 2021 7c. Co-Sponsor 3 Approval Date Jul 29, 2021 7c. Co-Sponsor 4 Approval Date 7c. Co-Sponsor 5 Approval Date 7c. Co-Sponsor 6 Approval Date 7c. Co-Sponsor 7 Approval Date 7c. Co-Sponsor 8 Approval Date 7c. Co-Sponsor 9 Approval Date 7c. Co-Sponsor 10 Approval Date 7e. CDA MG Approval Date 7f. FMG Approval Date 7g. V2 MG Approval Date 7h. Architecture Review Board Approval Date 7i. Steering Division Approval Date 7j. TSC Approval Date