HCS Ohio Data Repository tagging and jargon glossary

Categorical tags are used to help repository users identify and classify data and metadata in the repository. Descriptions of the tag groupings and tags are provided below.

Tagging groups

• Project / Dataset Name / Filename: human-friendly label and/or the file as stored.

• About / Description: short narrative summary of what the dataset contains.

• Metadata/Data: whether the file is analyzable data requiring secure access rights vs publicly-available documentation and supporting material.

• Study Component: which major programmatic bucket the dataset belongs to (e.g., PhotoVoice, PARTNER, administrative outcomes).

• Counties: which of two HCS Ohio county wave(s) the data pertain to.

• Primary Data Purpose: why the data were collected (the main analytic or operational intent).

• Data Type: the structural form of the data (survey, tracker, qualitative, etc.).

• Temporal Features: how often the data repeat (one-time vs monthly vs continuous, etc.).

• Primary Unit of Analysis: the level of data collection that the data primarily represent (person, organization, county, strategy, etc.).

• Topics: substantive domain(s) the dataset touches.

Metadata/Data

• Data: The file contains analyzable records (raw or cleaned) such as responses, events, counts, logs, trackers, or extracted measures. Data files need to be requested and are not visible to repository users until access rights have been granted.

• Metadata: The file primarily documents data rather than being the data itself—e.g., codebooks, crosswalks, variable lists, instruments, guidance, and annotations. These are publicly available without signing into an account.

Study Component

These tags indicate the major study module or repository section.

• HCS Project Information: Orientation/overview content for the repository itself (a great place to start when first orienting to the repository!).

• Administrative Outcome Data: County-level surveillance/administrative measures (often from state agencies), used for evaluating outcomes (e.g., overdose deaths, prescribing, naloxone distribution).

• Collaborative Workspace Records: Work-product and operational records from the HCS Ohio Basecamp collaboration platform. Typically used for documenting study operations, communications, and internal processes.

• Media Buy: Paid media campaign purchase and performance tracking (cost, duration, reach, placement), including creatives and approvals.

• PARTNER: Network/partnership survey data collected using the Visible Networks Lab PARTNER tool, including relational and non-relational organizational survey data.

• PhotoVoice: Participant-generated photo discussions and derived materials (transcripts, theme lists, codebooks, analyses, evaluation), separate from Qualitative Ohio Data.

• Qualitative Ohio Data: Qualitative interviews and related tracking from Ohio communities (e.g., coalition members, community organizations), separate from PhotoVoice, Stay Safe Study Data, and Sustainability Data.

• Stay Safe Study Data: Data from the Stay Safe Study focused on people who use drugs and fentanyl test strips (screeners, baseline, weekly surveys, test results, and qualitative). Separate from Qualitative Ohio Data.

• Sustainability: Post-intervention materials about sustainment of HCS strategies. Separate from Qualitative Ohio Data.

• Capacity-building Media Series: Recorded trainings/learning collaborative materials intended to build community capacity (webinars/modules).

• Survey and Study Collected Data: A catch-all repository category for survey/study-collected datasets.

• Core Data Collected by All HCS Sites: Data elements that exist across all four HCS research sites (Ohio plus other sites), enabling cross-site comparisons.

• Core Data Collected Only in Ohio: Data elements collected uniquely by the Ohio site (including research data and data for site-specific operational needs).

• Procedural and Planning Data: Supporting datasets created to run or organize the work (e.g., crosswalks, portals, internal workflows) that may still have analytic value.

• Costing Data: Datasets used to quantify costs and staff time associated with intervention or campaign activities (not costs of research).

Counties

These tags describe which set of HCS Ohio counties (and which wave) the dataset covers.

• Wave 1 County Data Only: Data restricted to Ohio Wave 1 communities/counties: Ashtabula, Athens, Cuyahoga, Darke, Greene, Guernsey, Hamilton, Lucas, Morrow (withdrew), Scioto.

• Wave 2 County Data Only: Data restricted to Ohio Wave 2 communities/counties: Allen, Brown, Franklin, Huron, Jefferson, Ross, Stark, Williams, Wyandot.

• Wave 1 and Wave 2 County Data: Data spanning both waves.

• Post-Intervention Data: Data collected after the intervention period, focused on sustainment or post-period outcomes/experiences.

• All or any Ohio counties: Statewide or non-wave-specific (e.g., Stay Safe files that can include participants/organizations from any Ohio location).

Primary Data Purpose

This is the “why collected” tag.

• Process Tracking: Tracks who did what and when (e.g., staffing, coding assignments, completion status), primarily operational.

• Demographics: Participant or respondent background characteristics (age, race/ethnicity, role, etc.), used for describing samples or stratifying analyses.

• Community Engagement and Interaction Logs: Records of meetings, contacts, participation, coalition processes, and engagement activities.

• Resource Tracking and Needs Assessment: Captures available services/resources, gaps/needs, and capacity characteristics (often county-level and organization-level).

• Fidelity and Evaluation and Reach Tracking: Fidelity measures whether intervention components were delivered as intended with a focus on adherence to planned steps. Evaluation and reach track whether strategies/campaigns happened, how they were implemented, and who/what they reached (often used for implementation evaluation).

• Experiential Description: Captures lived experience, perceptions, narratives, and contextual detail (often qualitative)..

• Photographic Artifacts: Inventories and metadata about participant-generated photos (filenames, dates, assignments), enabling linkage to discussions/analysis.

• Project Impact: Materials intended to evaluate the perceived or measured impact of a project/module (e.g., participant evaluation surveys; final codebook as analysis infrastructure).

• Socioecological Model Framework: Analytic products explicitly organized by a socioecological model (individual/interpersonal/community/system levels).

• Work process records: Operational records documenting the conduct of the study (tasks, work materials, artifacts).

• Participant Screening: Eligibility and recruitment/screening pipeline data (e.g., screeners, consort-style tracking).

• Behavioral Data: Self-reported behaviors (substance use, risk reduction, service use) and related measures.

• Study Outcomes: Outcome measures directly tied to primary and secondary study outcomes

Data Type

This is the structural form of the dataset/file.

• Questionnaire: Survey-style instrument with structured responses (individual- or organization-level).

• Tracker: Ongoing structured logging (often event- or time-period-based) used for monitoring, management, or fidelity/reach, typically completed by study staff.

• Meeting Records: Records of meetings (logistics, attendance, dates, agendas, notes).

• Economic: Cost/time/resource quantification data (budgets, staff time, spending, costing modules).

• Network: Data structured around relationships among actors (organizations/people), including networks, affiliations, and tie data.

• Qualitative: Text-based or qualitative-workflow datasets (e.g., NVivo projects, interview planning datasets when treated as qualitative infrastructure, metadata about qualitative data).

• Mixed Methods: Files combining qualitative and quantitative elements or serving a hybrid purpose (e.g., nominal group technique outputs, some evaluation instruments).

• Metadata: Documentation artifacts (codebooks, instruments, variable lists, crosswalks, annotation documents).

• Process artifacts: Non-tabular work products (e.g., creatives, approvals, media files, exports) that document processes and outputs.

• Administrative counts: Measures derived from administrative sources, typically aggregated counts by county and time period.

• Population counts: Denominators used for rate calculations (population estimates by county, age group, etc.).

• Test Results: Objective test outputs (e.g., oral-fluid drug testing results).

Temporal Features

This describes repetition frequency (how “time” behaves).

• One-Time: Collected once per unit (or effectively a single snapshot).

• Annual: Repeated yearly (e.g., yearly surveys, annual administrative measures).

• Monthly: Repeated each month (common for costing, fidelity trackers, reach reporting).

• Quarterly: Repeated each quarter (often administrative measures).

• Continuous: Updated on an ongoing basis without a fixed interval (event-driven or frequently updated trackers).

• Other Repeated Measures: Repeated, but not cleanly annual/monthly/quarterly (e.g., waves/rounds, periodic surveys, post-meeting surveys, or irregular follow-ups).

Primary Unit of Analysis

This indicates what a data record primarily represents.

People and groups

• Research Staff: Staff actions, assignments, time, or operational records.

• Community Members: Individuals in the community (often coalition members, residents, participants).

• People Who Use Drugs: Participants specifically characterized by drug use (often in Stay Safe and PhotoVoice contexts).

• Community Advisory Board: CAB member records.

Organizations and systems

• Community Organizations: Agencies/organizations operating in the community (services, coalitions, partners).

• Jails: County jail entities or jail-level measures.

• Providers: Clinicians or prescriber entities (provider-level measures).

Implementation objects

• Strategies: Intervention strategies (e.g., OEND, MOUD access, safer prescribing) tracked as discrete implementation objects.

• Communication Campaign / Media Campaign: Campaign-level records (materials, buys, reach, costing).

Geographies and event types

• County: County-level aggregation or information.

• Individuals: Individual-level records.

• Prescriptions: Measures derived from prescription events/episodes.

• Hospital visits: Measures derived from ED or hospital visit events.

• EMS events: Measures derived from EMS runs/events.

• Naloxone units: Distribution of naloxone kits.

Intervention scope

• CTH intervention at the community level: County/community-level intervention process measures (fidelity checklists, subcommittee checklists).

Topics

Process domains

• Research Process: How the study work was conducted (staffing, coding, workflow).

• Implementation: Planning, executing, monitoring, and sustaining intervention components.

• Resources and Mapping: Inventories of services, assets, and resource landscapes; mapping service availability and organizational roles.

• Community and Media Engagement: Coalition engagement, campaigns, communications, message exposure/retention, and community-facing interaction.

• Data Resources: Data dashboards, portals, data training needs, and data infrastructure for community decision-making.

• Economics: Costs, spending, resource inputs, and staff time associated with intervention activities.

• Community Partnerships: Network structure and partnership dynamics among organizations.

• Capacity-building: Training/technical assistance content intended to build skills or organizational capacity.

• Sustainability: Continuation of strategies post-intervention; sustainment capacity and plans.

Opioid-related and health outcome domains

• Experiences related to opioid epidemic: Narratives about opioid use disorder context, recovery, barriers, and community conditions.

• Naloxone Distribution: OEND strategies, events, kit distribution, and stocking. Separate from Jail naloxone distribution.

• Medication for Opioid Use Disorder: MOUD initiation, maintenance, referrals, supports, and service engagement.

• Fatal overdoses: Overdose mortality outcomes.

• Nonfatal overdoses: Overdose events not resulting in death, typically emergency medical services (EMS) or emergency department (ED)-treated.

• Opioid prescribing practices: Prescribing patterns and prescription risk indicators (high-dose, long duration, overlaps).

• MOUD linkage and initiation: Linkage to MOUD after overdose events; initiation pathways.

• MOUD prevalence: Counts/coverage of MOUD receipt in a population.

• MOUD treatment retention: Persistence on MOUD over defined periods (e.g., 180 days; person-months).

• OUD treatment – jails: MOUD induction/provision within jail settings and related services.

• Jail naloxone distribution: Provision of naloxone upon release or jail-based distribution.

• Substance Use Disorder: Broader SUD screening/diagnosis/service use measures beyond opioids alone.

• Hepatitis C: Screening/diagnosis/treatment measures for Hep C.

• HIV: HIV diagnosis measures

• Drug take-back: Disposal infrastructure (drop boxes) and related community prevention resources.

• Population denominator: Population estimates used as denominators in rate calculations.

Stay Safe Study domains

• Drug Use: Patterns and behaviors regarding substance use.

• Fentanyl Test Strips: FTS access/use, distribution practices, and related harm reduction behaviors.

Collaborative workspace domains

• Discussion threads; Task records; Internal study documentation: Work management artifacts (threads, tasks, documentation).

• Presentations; Videos: Media formats rather than domains, but functionally used as topical tags for discoverability.

Common dataset-name “tags” and abbreviations

These aren’t in the tag columns consistently, but they behave like tags for navigation and should be documented.

Prefixes

• SMS –: A data collection module label common to REDCap-based data collection projects that were used across the four HCS sites, not just Ohio.

• HCS### – (e.g., HCS048, HCS072): Ohio site-specific REDCap-based dataset numbering scheme.

• T1 / T2 – (PARTNER files): Timepoint labels for PARTNER data collections (T1 in Jul 2022 and T2 in Jan 2024).

PARTNER file suffixes

• RD: Relational data (ties/ratings between organizations).

• NRD: Non-relational organization survey data (organization attributes/resources).

• IS: PARTNER-calculated indicator scores (network metrics such as centrality, trust/value measures). This is distinct from IS used to mean “Implementation Science” elsewhere.

Rounds and waves embedded in names

• Round 1/2/3/4…: Repeated survey rounds (often annual or periodic, not necessarily aligned to wave labels).

• W1 and W2: Wave 1- and Wave 2-specific datasets.

Intervention strategy abbreviations

Note that often “W1” is not explicitly marked for Wave 1 tools, but “W2” is added for Wave 2 tools that had a Wave 1 counterpart.

• CTH: Communities That HEAL (intervention framework).

• OEND: Overdose education and naloxone distribution.

• MOUD: Medication for opioid use disorder.

• ORCCA / ORCCAT2 / ORCW2: Strategy/action-plan implementation tracking instruments (Wave 1 vs Wave 2 variants) for the Opioid-overdose Reduction Continuum of Care Approach.

• TTAT: Training and technical assistance tracker.

• PIM: Participant Information Module (information about assets/organizations/individuals).

• CEQ: Campaign Evaluation Questionnaire (CEQ2…CEQ7 are repeated rounds).

• BQD / CBS: Baseline Qualitative Demographics / Coalition Baseline Survey (and numbered rounds like BQD4, CBS4).

• FMSC / FMSCW2: Fidelity Measures Subcommittee Checklist (Wave 1 vs Wave 2 variants).

PhotoVoice session naming

• Orientation: Typically Session 1 (intro + demographics + topic brainstorming).

• Main Session #1: Typically Session 2 (SHOWED model-based discussion).

• Main Session #2: Typically Session 3 (SHOWED model-based discussion).

• Final / Dissem(emination): TypicallySession 4 (sharing and discussing preliminary analyses).

Administrative Outcome Data terms

Medicaid data: Administrative claims data originating from the Ohio Department of Medicaid (ODM) reported in aggregate.

ODM: Ohio Department of Medicaid.

Administrative data: Data reported from state agencies to the HEALing Communities Study (HCS), typically as counts or rates at the county level in annual, quarterly, or monthly timespans. Includes nonfatal and fatal overdose death data, prescription data, Medicaid claims data, EMS/syndromic sources, etc. Some de novo data – such as data collected about and from county jails – are also included as administrative data.

PDMP: Prescription Drug Monitoring Program, a generic term for Ohio’s Automated Rx Reporting System (OARRS) operated by the Ohio Board of Pharmacy (BoP). Data from OARRS is often referred to as “PDMP data.”

OARRS: Ohio Automated Rx Reporting System (Ohio’s PDMP).

BoP: Ohio Board of Pharmacy, the operational home of Ohio’s PDMP, OARRS.

ODH: Ohio Department of Health, the source of vital statistics/mortality/overdose death data in the Administrative Outcome Data.

Death data: Overdose death measures in the administrative outcome measure set reported by the Ohio Department of Health—specifically Measures 1, 1.1–1.6, 2.1, and 2.1.1–2.1.6.

EMS run data: Emergency medical service (EMS) event measures—specifically Measures 2.8.1 and 2.8.2 (EMS naloxone administration and suspected opioid overdose EMS events) in the Administrative Outcome Data

HCS instruments and implementation terms

FMC: Fidelity Monthly Checklist, data collected for study fidelity measurement

ORCCA: Opioid-Overdose Reduction Continuum of Care Approach, an intervention concept accompanied by a family of tracking tools/datasets (e.g., ORCCA trackers, TAG)..

TAG: Technical Assistance Guide, a technical assistance guide associated with ORCCA.

PIM: Participant Information Module, a REDCap-based data collection tool used by all HCS sites (including Ohio) to capture community assets/participants/organizations to support networked or directory-like use.

Qualitative interviews

IS Coalition Member Interviews: Implementation Science (IS) qualitative interviews conducted with coalition members. In HCS contexts, “IS” is commonly used as shorthand for Implementation Science workstreams (e.g., qualitative interviews about implementation processes and context). “IS” also shows up in PARTNER data to mean “indicator scores”.

IS Partner Organization Interviews: Implementation Science (IS) qualitative interviews conducted with partner organizations. Here, partner organizations are organizations in HCS communities involved in the effort to combat the opioid crisis and is distinct from PARTNER as a dataset.

Search term support

Some terms might show up only within files and not in the components of the repository that are searchable. Below is a guide to help identify search terms that will help repository users tap into data concepts. In general, it will be useful to start with HCS Project Information (accessible from the repository homepage) for most datasets and the Measure Technical Specifications for Administrative Outcome Data to learn what data are available and how to request/find those data.

What users might want to search for → What the repository calls it

• Medication-Assisted Treatment (MAT) → search MOUD

• buprenorphine / Suboxone / Sublocade → search MOUD

• methadone / Methadose → search MOUD

• naltrexone / Vivitrol / Revia → search MOUD

• naloxone / Narcan / Kloxxado → search OEND

• prescription monitoring / prescribing data → search PDMP and OARRS

• overdose death statistics / fatal overdoses → search Administrative Outcome Data (and M_1 / M_2_1 patterns after obtaining access to data files).

• EMS overdose calls / naloxone administration by EMS → search Administrative Outcome Data (and M_2_8_1 / M_2_8_2 after obtaining access to data files).

• FMC / study fidelity monthly forms → search Fidelity Measures.