<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="5848" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://www.socictopen.socict.org/items/show/5848?output=omeka-xml" accessDate="2026-04-18T09:44:18+00:00">
  <fileContainer>
    <file fileId="5848">
      <src>https://www.socictopen.socict.org/files/original/ed137f5c52bf5b3a1bb728c97593bd71.pdf</src>
      <authentication>d90b4c7fb8ad43d791c89a891ffd78a8</authentication>
    </file>
  </fileContainer>
  <collection collectionId="1">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1">
                <text>Coronavirus</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2">
                <text>Dominio científico: Coronavirus</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="1">
    <name>Text</name>
    <description>A resource consisting primarily of words for reading. Examples include books, letters, dissertations, poems, newspapers, articles, archives of mailing lists. Note that facsimiles or images of texts are still of the genre Text.</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="52206">
              <text>Implementation of peer recovery coach services for opioid overdose patients in emergency departments in Indiana: findings from an informal learning collaborative of stakeholders.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="52207">
              <text>Monte D Staton, Dennis P Watson, Dillon Thorpe</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="52208">
              <text>The Recovery Coach and Peer Support Initiative (RCPSI) in Indiana focused on implementing peer recovery coaches (PRCs) to engage opioid overdose patients in emergency department (ED) settings and promote entry into recovery services. State workers and researchers organized an informal learning collaborative primarily through teleconference meetings with representatives of 11 health service vendors to support implementation. This study presents qualitative analysis of the teleconference meeting discussions that guided RCPSI implementation to display how the informal learning collaborative functioned to support implementation. This informal learning collaborative model can be applied in similar situations where there is limited guidance available for a practice being implemented by multidisciplinary teams. Authors conducted a thematic analysis of data from 32 stakeholder teleconference meetings held between February 2018 and April 2020. The analysis explored the function of these collaborative teleconferences for stakeholders. Major themes representing functions of the meetings for stakeholders include: social networking; executing the implementation plan; identifying and addressing barriers and facilitators; educating on peer recovery services and target population; and working through data collection. During the last 2 months of meetings, stakeholders discussed how the COVID-19 pandemic created multiple barriers but increased use of telehealth for recovery services. Teleconference meetings served as the main component of an informal learning collaborative for the RCPSI through which the vendor representatives could speak with each other and with organizers as they implemented the use of PRCs in EDs.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="52209">
              <text>2021</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="52210">
              <text>covid-19, telehealth, emergency department, Opioid use disorder, Peer recovery coach</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="52211">
              <text>10.1093/tbm/ibab031</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="52212">
              <text>Translational behavioral medicine</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
