goodthingswithdata.comExemplar presentations · 4 of 7

A scrappy little division that cares a lot about data: a vision for data sciences in DTBE

Chad Heilig — Division of Tuberculosis Elimination, CDC, 2014-03-06 — 49 slides (47 shown; 2 omitted)

This rendering was constructed from an original PowerPoint presentation. Corrections of original text are indicated as “[corrected: X]”, redactions as “[redacted: X]”, and names withheld as “[generalized: X]”. Handouts and other auxiliary sources mentioned in the presentations are not available. The content of each presentation was believed to be correct and valid at the time of the presentation. This content, including references and links within the slides, has not been checked or updated when preparing this site. This rendering was facilitated by Anthropic Claude agentic tools for automated text extraction through computer vision and for assistance with compiling the completed sets.

Setting: A scrappy little division that cares a lot about data: a vision for data sciences in DTBE, 2014-03-06. CDC’s Division of Tuberculosis Elimination.

2014-03-06, warm and breezy. Today I led a presentation that was the offspring of 2 parents: (1) the director of my center, who went around to every division and branch to learn what we do, and (2) a think tank that I led of colleagues with equally little standing but plenty of opinions-turned-evidence. With my branch chief’s full support, I met today’s moment in PowerPoint for “A Scrappy Little Division That Cares a Lot about Data: A Vision for Data Sciences in DTBE”. Hallmark Shoebox meets bureaucrats who care. It’s the first time I’ve used the phrase “data science” with a group. I haven’t figured out whether it’s a vacuous buzz phrase or the key to cracking this thing open. Thinking about data science tasks end to end through a shift in data culture. DTBE is ready; they’re doing most of it already. I want to help them make commitments: a foundation of well-supported tools, mediated rather than haphazard cross-branch problem-solving and sharing and archiving. Like last year’s talk, this one felt magical.

I meant for this presentation to feed into ongoing strategic planning within DTBE for research, program, and staffing, motivated by DTBE’s internal think tank.

Related works, not cited

Full references: this page · whole site, by domain (opens in a new tab) · whole site, by type of work (opens in a new tab)

Slide 1A scrappy little division that cares a lot about data: a vision for data sciences in DTBE

Faded background of 4 charts in a 2-by-2 grid, overlaid with diagonal pink and cyan hatching, behind the title text.

Chad Heilig, PhD
Division of Tuberculosis Elimination
2014-03-06

Abbreviations: DTBE = Division of Tuberculosis Elimination (CDC).

Slide 2[figures: cases of TB averted]

Four tuberculosis charts in a 2-by-2 grid: monthly cases, incidence trends by birthplace, cases averted, and incidence projections to 2060.
Description

Figure 1

Panels
1 (top left)
Elements
1 jagged black line depicts monthly counts of tuberculosis cases over time
Horizontal
Year, 1993–2013, ticks every 2 years; data run from 1993 to the end of 2012
Vertical
Tuberculosis cases, 0–2,500, ticks every 500; data span about 480 to 2,400
Visible pattern
The line zigzags in an annual saw-tooth pattern falling from left to right.

Figure 2

Panels
1 (top right)
Elements
3 series in 3 colors (purple, black, teal), each of about 20 annual dots with a line, labeled Foreign-born, Total and US-born
Horizontal
Year, 1993–2013, ticks every 2 years; data 1993–2012
Vertical
Tuberculosis cases per 100,000 population, logarithmic scale with ticks at 1, 2, 5, 10, 20 and 40; extent 1 to about 40
Visible pattern
All three series fall from left to right in nearly straight lines on the log scale, with Foreign-born on top, Total in the middle, and US-born at the bottom.

Figure 3

Panels
1 (bottom left)
Elements
Filled region between line graph of cases averted (bottom) and cases projected at 1993 rate (top).
Horizontal
Years, 1993–2013, ticks every year
Vertical
Case counts, 10,000–30,000, ticks every 5,000; no zero
Visible pattern
The 2 step lines start together at about 25,000 in 1993 and diverge. The region between them is shaded in purple (foreign-born cases averted) and teal (US-born cases averted).

Figure 4

Panels
1 (bottom right)
Elements
2 groups (purple for Foreign-born, teal for U.S.-born), each with 2 shaded bands, 1 bounded by solid lines and 1 by dashed lines; legend gives baseline and 2 × baseline lines for USB and FB
Horizontal
year, 2000–2060, ticks every 10 years
Vertical
incidence/million/year, logarithmic scale with ticks at 1, 2, 5, 10, 20, 50, 100, 200 and 300; extent 1 to about 300; dotted horizontal reference line at 1
Visible pattern
The Foreign-born bands decline gently and level off, the solid band ending between about 90 and 130 at 2060 and the dashed band between about 55 and 75. The U.S.-born bands fall more steeply: the solid band ends between about 2 at 2060 and well below 1; the dashed band lies below it.

Text in the picture

Monthly cases of TB, 1993–2012
Tuberculosis cases
Year
Trend in incidence of TB per 100,000 population 1993–2012
Tuberculosis cases per 100,000 population
Foreign-born
Total
US-born
Year
234,000 cases of TB averted since 1993
51,000 foreign-born
cases averted
case count
at 1993 incidence
183,000 US-born
cases averted
observed case count
Year
Range of TB incidence projections from best-fit parameters
Doubling the rate of treatment of LTBI
Foreign-born
incidence/million/year
U.S.-born
baseline USB
baseline FB
2 × baseline USB
2 × baseline FB
reported
year

Abbreviations: FB = foreign-born; LTBI = latent tuberculosis infection; TB = tuberculosis; US = United States; USB = US-born.

Slide 3“A scrappy little division that cares a lot about data”

Slide 3: “A scrappy little division that cares a lot about data”; its text follows
  • Scrappy: resourceful, uncowed
    • Imminently pragmatic; how to ensure robustness?
  • Cares a lot: committed to quality, mission
    • Public service, improving human condition
  • About data: pieces of information, support development of knowledge
    • Evidence base for better, more enduring success

Slide 4Overview

Slide 4: Overview; its text follows
  • Motivation: DTBE Think Tank*
  • Meaning of “data science”
  • How DTBE practices data sciences now
  • A vision for data sciences in DTBE

* Winner of DTBE Director’s Quarterly Recognition Award for the First Quarter of 2014

Abbreviations: DTBE = Division of Tuberculosis Elimination (CDC).

Slide 5DTBE think tank: on research

Slide 5: DTBE think tank: on research; its text follows
  • Create a “data science activity” to ensure considerations of core research principles and build research capacity
    • Study design and research methodology
    • Data management and statistics
    • Survey or questionnaire design
  • More data and analytic support for current research and for program evaluation, surveillance, and NTIP

Abbreviations: DTBE = Division of Tuberculosis Elimination (CDC); NTIP = National Tuberculosis Indicators Project (CDC).

Slide 6DTBE think tank: on work force

Slide 6: DTBE think tank: on work force; its text follows
  • Greater depth in data management and analysis for all data-driven research and nonresearch activities
    • Surveillance, evaluation, other program data, novel methods
  • Cross-branch coordination of data-centered efforts and expertise
  • Modest increase in FTEs in data sciences (potential net decrease in other areas)
    • Statisticians, quantitative epidemiologists, information technology specialists; add economics

Abbreviations: DTBE = Division of Tuberculosis Elimination (CDC); FTEs = full-time equivalents (staff positions).

Slide 7Meaning of “data science”

Slide 7: Meaning of “data science”; its text follows

Slide 8Data science

Slide 8: Data science; its text follows
  • Study of generalizable extraction of knowledge from data
  • Builds on techniques and theories from many fields with goal of extracting meaning from data and creating data products
    • Data engineering, computing and information sciences, scientific method, mathematics and statistics, visualization

Slide 9Data scientists

Slide 9: Data scientists; its text follows
  • Solve complex data problems through employing deep expertise in some scientific discipline
  • Often work with various elements of math, stats, computer science
  • Practice as team – expertise and proficiency across disciplines

Slide 10Data science tasks: end to end

Slide 10: Data science tasks: end to end; its text follows
  • Protocol development
    • Relate scientific questions, hypotheses to data needs
    • Data collection: instruments, procedures, management, security
  • Quality assurance
    • Gather, enter, organize, manage data
  • Data construction
    • Combine data elements to address questions
  • Data analysis
    • Create visualizations to aid in understanding data
    • Build mathematical models using data
  • Communicate data insights to specialists, laypersons
  • Archive, disseminate data

Slide 11How DTBE practices data sciences

Slide 11: How DTBE practices data sciences; its text follows

Abbreviations: DTBE = Division of Tuberculosis Elimination (CDC).

Slide 12Examples of data science activities (1)

Slide 12: Examples of data science activities (1); its text follows
  • Surveillance (NTSS, TB GIMS)
    • Complex, HL7-compliant system, fed by dozens of jurisdictions using varied technologies
    • Relies on relationship with CSELS
    • Semiautomated flagging of potential clusters
    • Stewardship for regular and investigator-initiated analysis, including NTIP
  • Outbreak investigations
    • Ad hoc needs for site-specific data applications

Abbreviations: CSELS = Center for Surveillance, Epidemiology, and Laboratory Services (CDC); GIMS = Genotyping Information Management System (TB GIMS, CDC); HL7 = Health Level Seven (standards for exchanging health data); NTIP = National Tuberculosis Indicators Project (CDC); NTSS = National Tuberculosis Surveillance System (CDC); TB = tuberculosis.

Slide 13Examples of data science activities (2)

Slide 13: Examples of data science activities (2); its text follows
  • TB Trials Consortium
    • Resource-intensive development of data systems
    • Incremental system changes across trials (>10,000 pts)
      • Increasing web-based entry at study sites
    • New commitment to CDISC standards, modular
      • CDISC-conforming public-use data
    • Most statistical design, analysis in-house
  • TB Epidemiological Studies Consortium
    • Resource-intensive development of data systems
    • Statistical design in-house; analysis in planning

Abbreviations: CDISC = Clinical Data Interchange Standards Consortium; TB = tuberculosis.

Slide 14Examples of data science activities (3)

Slide 14: Examples of data science activities (3); its text follows
  • PETTS
  • Kenya-based projects
  • Cambodia registers
  • Botswana clinics
  • 3HP post-marketing
  • Lab branch data systems
  • Social media analytics

Abbreviations: 3HP = 3 months of once-weekly isoniazid (H) plus rifapentine (P): the 12-dose regimen for latent TB infection; PETTS = Preserving Effective TB Treatment Study.

Slide 15Examples of data science activities (4)

Slide 15: Examples of data science activities (4); its text follows
  • Systematic review and meta-analysis
  • Modeling scenarios
    • TB elimination in US
    • Cost-effectiveness
      • 12-dose INH/RPT regimen vs 270-dose INH
      • Structural interventions on immigration
      • Treatment approaches in outbreak response

Abbreviations: INH = isoniazid; RPT = rifapentine; TB = tuberculosis; US = United States.

Slide 16Noteworthy features

Slide 16: Noteworthy features; its text follows
  • Strong staff foundation (>40 persons)
  • Strong on protocols, data collection plans
  • Most development and maintenance of large data systems is contracted
    • Field sites (BW, KE, TH) have their own systems
  • Most small data systems managed ad hoc
  • Most data analysis now in-house
    • Except some specialized or collaborative (e.g., pharmacometrics)

Abbreviations: BW = Botswana; KE = Kenya; TH = Thailand.

Slide 17Areas to strengthen

Slide 17: Areas to strengthen; its text follows
  • Connections between tasks from one end to the other end, especially smaller projects
    • “Get the data now; figure it out later.”
    • Connect forms to data entry to data management to data analysis to data presentation to data archiving
    • Anticipate all data personnel and methods
    • Documentation of data, analysis
  • Awareness and coordination across branches
    • Fragmentation of tools to manage, analyze data
  • Strength and innovation in less common methods

Slide 18A vision for data sciences in DTBE

Slide 18: A vision for data sciences in DTBE; its text follows

Intended to feed into ongoing strategic planning within DTBE for research, program, and staffing.

Abbreviations: DTBE = Division of Tuberculosis Elimination (CDC).

Slide 19Overview of vision for DTBE: Culture and commitments

Slide 19: Overview of vision for DTBE: Culture and commitments; its text follows
  • Principles and practices
    • Scientifically valid, valuable; division priority
    • Manageable systems, all sizes
    • Rigorous, credible data collection, analysis
  • Tools and technology
    • Important concepts
    • Development tiers
    • Supported software
  • Staffing
    • Disciplines, skills, roles, and organization
    • Communicating, training, mentoring, and leadership

Abbreviations: DTBE = Division of Tuberculosis Elimination (CDC).

Slide 20Principles and practices: Valid, valuable, priority

Slide 20: Principles and practices: Valid, valuable, priority; its text follows
  • Because we are talking about commitment of DTBE resources, some scarce
    • Scientifically valid
    • Valuable
    • Division priority

Abbreviations: DTBE = Division of Tuberculosis Elimination (CDC).

Slide 21Principles and practices: Manageable systems, all sizes

Slide 21: Principles and practices: Manageable systems, all sizes; its text follows
  • Well-planned life cycle
    • Scope
    • Effort
    • Implementation and continuity
    • Likely successful completion
    • Archiving
  • Realistic planning, management of data resources

Slide 22Principles and practices: Quality data before and after

Slide 22: Principles and practices: Quality data before and after; its text follows
  • Support interchange, continuity, archiving
  • Adopt common conventions and standards
    • Controlled vocabulary (e.g., sex/gender, race/ethnicity, country, AFB smear result)
    • Data collection modules
    • Data structures
    • Calibrate to level of data activity
      • Full conformance vs basic utility (e.g., trials for FDA vs smaller studies for public use)
    • HL7, CDASH, CDISC, WHODD, MedDRA, …
  • Program well: SAS (including SQL), R

Abbreviations: AFB = acid-fast bacilli; CDASH = Clinical Data Acquisition Standards Harmonization (a CDISC standard); CDISC = Clinical Data Interchange Standards Consortium; FDA = Food and Drug Administration (US); HL7 = Health Level Seven (standards for exchanging health data); MedDRA = Medical Dictionary for Regulatory Activities; SQL = Structured Query Language; WHODD = WHO Drug Dictionary.

Slide 23Principles and practices: Quality data during, throughout

Slide 23: Principles and practices: Quality data during, throughout; its text follows
  • Assure quality during data collection
    • Check during or shortly after entry
    • Internal consistency of closely related elements
  • (e.g., collect, validate, store dates-times, durations)
  • Construct analytic data early and often
    • Esp. complicated relationships across disparate elements (“acquired MDR”, “completed therapy”)
    • Early sense for ability to address analytic aims, remediate problems as soon as possible
    • Rapid completion of main analysis after final data

Abbreviations: MDR = multidrug-resistant (tuberculosis).

Slide 24Tools and technology: Important concepts

Slide 24: Tools and technology: Important concepts; its text follows
  • Regulation, security, ethics
    • Human subjects, Paperwork Reduction Act, Privacy Act, HIPAA Privacy Rule, FISMA, C&A, EPLC
      • “Human subject”, “information”, PII, PHI
      • Anonymous, de-identified, coded
    • Confidentiality
    • Security
  • Source documentation, traceability
  • Programming, documentation

Abbreviations: C&A = certification and accreditation; EPLC = Enterprise Performance Life Cycle (HHS/CDC framework for managing IT projects); FISMA = Federal Information Security Management Act (2002; Modernization Act 2014); HIPAA = Health Insurance Portability and Accountability Act (1996); PHI = protected health information; PII = personally identifiable information.

Slide 25Tools and technology: Development tiers

Slide 25: Tools and technology: Development tiers; its text follows
  • Vision: 3 data development channels
    • Do-it-yourself, with basic guidance (e.g., EpiInfo)
    • Small-scale, assisted development within DTBE
  • (e.g., Microsoft Access)
    • Large-scale, intensive development outside DTBE
  • (e.g., Microsoft SQL Server)
  • Common practices for all 3 channels
    • Mature data collection items before development
    • Support for data conventions, standards
    • Ongoing life-cycle management
      • Primary, in-house business analyst/consultant
      • As needed, out-source additional assistance

Abbreviations: DTBE = Division of Tuberculosis Elimination (CDC); SQL = Structured Query Language.

Slide 26Development tier 1: Do-it-yourself, basic guidance

Slide 26: Development tier 1: Do-it-yourself, basic guidance; its text follows
  • Examples: field site program evaluations
  • Develop own data entry, storage
  • DTBE should promote, support good practices
    • Choices of software (friends don’t let friends use Excel for data entry)
    • Methods for data entry and coding
    • Support for specified choices; not prevented from using other tools

Abbreviations: DTBE = Division of Tuberculosis Elimination (CDC).

Slide 27Development tier 2: Small-scale, assisted development

Slide 27: Development tier 2: Small-scale, assisted development; its text follows
  • Example: 3HP post-marketing
  • In-house assistance and collaboration
    • Could involve working with field staff (e.g., KE)
  • DTBE commitment to selected current, future platforms and standards
    • Off the shelf, e.g., Microsoft Access, MySQL
    • Minimum # staff with skills in selected platforms
    • Endorse, implement industry standards

Abbreviations: 3HP = 3 months of once-weekly isoniazid (H) plus rifapentine (P): the 12-dose regimen for latent TB infection; DTBE = Division of Tuberculosis Elimination (CDC); KE = Kenya.

Slide 28Development tier 3: Large-scale, intensive development

Slide 28: Development tier 3: Large-scale, intensive development; its text follows
  • Examples: TBTC, TBESC 2, NTSS
  • Application development
    • Substantial assistance outside of DTBE
    • Expensive
    • Subject to process controls
    • Enforced quality assurance, security

Abbreviations: DTBE = Division of Tuberculosis Elimination (CDC); NTSS = National Tuberculosis Surveillance System (CDC); TBESC = Tuberculosis Epidemiologic Studies Consortium (CDC); TBTC = Tuberculosis Trials Consortium (CDC-sponsored).

Slide 29Tools and technology: software

Slide 29: Tools and technology: software; its text follows
  • 3 tiers of software support
    • Core: Access, SAS (incl. SQL), R
    • Limited: Excel, EpiInfo
    • Minimal or none: SPSS, Stata
    • Specialized, ad hoc: TreeAge, NetLogo, ArcGIS

Abbreviations: SQL = Structured Query Language.

Slide 30Tools and technology: innovation in methods and applications

Slide 30: Tools and technology: innovation in methods and applications; its text follows
  • Example: individual-based models
  • Continue development of innovative methods
    • IBM for compartmental models, transmission models
    • Systematize sensitivity analyses
  • Teach scientists new schemas
    • What questions lend themselves to these innovative methods? What are the limitations?
  • Make methods available as feasible
    • Teach scientists to implement their own models

Abbreviations: IBM = individual-based model.

Slide 31Staffing: data science core

Slide 31: Staffing: data science core; its text follows
  • 3 senior scientists: math/stats, epi, info mgmt
  • Link DTBE priorities to data science resources
  • Consult early on data project life cycle
    • Boundaries, expectations, level of effort
  • Raise awareness of problems, solutions
    • Weekly data sciences methods meeting (~10 people)
    • 2–3 methods reading groups per year
    • Regulation and policy (e.g., confidentiality, security, sharing)
  • Broker cross-branch collaboration, mentoring

Abbreviations: DTBE = Division of Tuberculosis Elimination (CDC).

Slide 32Staffing: specialized skills, roles

Slide 32: Staffing: specialized skills, roles; its text follows
  • Enhanced support for development life cycle:
  • designated consultant(s) to advise
    • Protocol*
    • Data elements, including standards
    • Data systems, including regulation and security
    • Data analysis, including methods
  • Underrepresented disciplines (e.g., economics)
  • Referrals to other resources, as needed
    • Might recommend to out-source business analysis, requirements analysis

* Recommended by think tank; goes beyond data systems

Slide 33Staffing: distributed skills, roles

Slide 33: Staffing: distributed skills, roles; its text follows
  • Within-branch practices (esp. epi, stats) supported by experienced scientists, analysts
    • Where possible, build capacity within branches
    • Early planning for advanced needs outside branch
  • (e.g., splines, recursive partitioning)
  • Cross-branch sharing of data, analysis practices
  • Ongoing mentoring

Slide 34Conclusion: a shift in data culture

Slide 34: Conclusion: a shift in data culture; its text follows
  • Total number of data science staff (FTE+contractors) is likely close to meet anticipated needs
    • Location, distribution, configuration could be evaluated
    • More, earlier involvement of experienced data scientists could require modest additional capacity
    • Need explicit succession planning to ensure continuity
  • A few new roles are contemplated
    • “Data science core” cross-branch leadership
    • Advisor(s) over data system life cycle
    • Might improve coverage of some disciplines (econ)
  • No specific organizational proposal at this time

Abbreviations: FTE+contractors = full-time equivalent (staff) plus contractors.

Slide 35Conclusion: commitments

Slide 35: Conclusion: commitments; its text follows
  • Set of well-supported tools
    • Set a reliable foundation, not limit options; requires ongoing (though not large) investment
  • Cross-branch problem-solving and sharing
    • Already happens, often haphazardly; make more systematic but not institutionally burdensome
    • To be led and mediated by data science core
  • Sharing and archiving (esp. data and code)

Slide 36Discussion

A redacted region below the title and the web address.

[redacted: email address]
www.cdc.gov/tb

Slide 37 is omitted.

Slide 38[random non sequiturs]

Slide 38: [random non sequiturs]; its text follows
  • Hypothesis-driven methods are largely antithetical to discovery and knowledge promotion, in part because models are always wrong and experiments are tailored to narrow claims
  • Main value: honesty in characterization of premises, argument, and aims (avoid post hoc diversion)
  • Need methods for knowledge production that are open, robust, credible
  • Randomization has limited utility in clinical trials, relating to narrow objectives
  • Far more important: quality of execution and mitigation of potential bias – fancy prospective cohorts
  • Rather have good data and a strong scientific goal with a poorly articulated statistical plan than poor data with weak scientific goal and a pristine statistical design

Slide 39Sample strategies for taming data

Slide 39: Sample strategies for taming data; its text follows
  • Hierarchy of data structures
    • Within test (smear, culture, Xpert)
    • Within specimen, across tests
    • Within participant encounter*, across specimens
    • Across participant encounters
  • Date-based events by actual date rather than expected schedule
  • Define, refine data constructs to support multiple analytic goals (use experience)

Abbreviations: Xpert = Xpert MTB/RIF (Cepheid GeneXpert cartridge nucleic acid amplification test for TB and rifampicin resistance).

Slide 40Generalized goals for taming data

Slide 40: Generalized goals for taming data; its text follows
  • Learn about data: analyze before, during, after
  • Learn from data: analyze during, after
  • Proceed incrementally, iteratively, responsibly
    • Small steps, build up complex logic
      • Modular: Mtb/NTM/contamination; DST; doses
    • Refine, evolve
    • Document, vet, guard

Abbreviations: DST = drug susceptibility testing; Mtb = Mycobacterium tuberculosis (the bacterium that causes TB); NTM = nontuberculous mycobacteria.

Slide 41Recurring complex data, beyond lab

Slide 41: Recurring complex data, beyond lab; its text follows
  • More lab and diagnostic data (pediatric)
  • Ill-defined endpoints (hypersensitivity)
  • Flexibility in date-based events (SQL!)
    • TBTC DOT, initial and continuation?
    • TBTC self-administered 12-dose regimen
    • TBESC LTBI cohort
    • Diagnostic and treatment patterns
    • Endpoints in DR TB

Abbreviations: DR = drug-resistant (DR TB = drug-resistant tuberculosis); LTBI = latent tuberculosis infection; SQL = Structured Query Language; TB = tuberculosis; TBESC = Tuberculosis Epidemiologic Studies Consortium (CDC); TBTC = Tuberculosis Trials Consortium (CDC-sponsored).

Slide 42S28 date-based SQL code snippet

Screenshot of code in an editor, with syntax coloring, formatting marks shown and the first line highlighted in light blue.
Description

Text in the picture (summary)

SAS/SQL code with a 15-line comment and 21-line Proc SQL Select statement to determine culture conversion and stable conversion.

Abbreviations: S28 = TBTC Study 28 (moxifloxacin vs isoniazid in the intensive phase of TB treatment); SQL = Structured Query Language.

Slide 43ID-TB/HIV incomplete 4×7

Slide 43: ID-TB/HIV incomplete 4×7; its text follows
Sput 1Sput 2Sput 3UrineStoolBloodLNA‡
Smear•••••—•
LJ 1•••••••
LJ 2•••••••
MGIT†††††††
  • Every specimen
  • Every specimen in TH, VN (but not KH)
  • Indicated for LN ≥1 cm (≥2 cm inguinal)

Abbreviations: HIV = human immunodeficiency virus; ID = Improving Diagnosis of TB in People Living with HIV (study); KH = Cambodia; LJ = Löwenstein–Jensen (egg-based solid culture medium for mycobacteria); LN = lymph node; LNA = lymph node aspirate; MGIT = Mycobacteria Growth Indicator Tube (liquid culture system); TB = tuberculosis; TH = Thailand; VN = Vietnam.

Slide 44[corrected: Kenya ICF 4×7]

Slide 44: [corrected: Kenya ICF 4×7]; its text follows
Initial visitFollow-up visits
Spot Sput 1Spot Sput 2Morn SputLNA‡StoolSpot Sput 1[corrected: Spot Sput 2]
Fluor••••••
MGIT••••••
ZN••
Xpert•†
  • Every specimen
  • If sufficient volume
  • Indicated for LN ≥1 cm (≥2 cm inguinal)

Abbreviations: ICF = intensified case finding; LN = lymph node; LNA = lymph node aspirate; MGIT = Mycobacteria Growth Indicator Tube (liquid culture system); Xpert = Xpert MTB/RIF (Cepheid GeneXpert cartridge nucleic acid amplification test for TB and rifampicin resistance); ZN = Ziehl–Neelsen (acid-fast stain for smear microscopy).

Slide 45Data scientists

Slide 45: Data scientists; its text follows
  • “The information and computer scientists, database and software and programmers, disciplinary experts, curators and expert annotators, librarians, archivists, and others, who are crucial to successful management of a digital data collection”
  • “Assists in the planning, collection, transformation, analysis, and reporting of clinical trial data and communication of their results. … crucial to determination of safety and efficacy of novel therapeutic compounds.”

Slide 46Paradoxes (1)

Slide 46: Paradoxes (1); its text follows
  • Inventor’s paradox: can be easier to solve a more general problem than a specific type of problem; identify prospects based on experience; e.g., methods and principles of QA/QC and of constructing analytic data sets
  • Prevention paradox: majority of cases of disease come from population with low or moderate risk; minority from high-risk populations → for 1 person to benefit, many have to change behavior with no benefit or slight harm/disadvantage

Abbreviations: QA = quality assurance; QC = quality control.

Slide 47[un]known [un]known

Borderless 2-by-2 table whose cell numbers are red; the 4 is bold and a brighter red than 1, 2 and 3. The numbers in the quotation are red too.
  • As we know,
  • There are known knowns. 1
  • There are things we know we know.
  • We also know
  • There are known unknowns. 2
  • That is to say
  • We know there are some things
  • We do not know.
  • But there are also unknown unknowns, 3
  • The ones we don't know
  • We don't know.
  • Donald Rumsfeld, [corrected: 2002-02-12], Department of Defense news briefing
We do [not] knowthat we do [not] / know
DoDo not
Do12
Do not43

Slide 48 is omitted.

Slide 49Paradoxes (2)

Slide 49: Paradoxes (2); its text follows
  • Service recovery paradox: better satisfaction to be seen remediating flaw than having no such flaw at all
  • Induced demand / reduced demand: increase supply → more consumption; decrease capacity → reduce demand
    • Solutions: increase costs, allocate/meter/coordinate control

Abbreviations

3HP = 3 months of once-weekly isoniazid (H) plus rifapentine (P): the 12-dose regimen for latent TB infection; AFB = acid-fast bacilli; BW = Botswana; C&A = certification and accreditation; CDASH = Clinical Data Acquisition Standards Harmonization (a CDISC standard); CDISC = Clinical Data Interchange Standards Consortium; CSELS = Center for Surveillance, Epidemiology, and Laboratory Services (CDC); DR = drug-resistant (DR TB = drug-resistant tuberculosis); DST = drug susceptibility testing; DTBE = Division of Tuberculosis Elimination (CDC); EPLC = Enterprise Performance Life Cycle (HHS/CDC framework for managing IT projects); FB = foreign-born; FDA = Food and Drug Administration (US); FISMA = Federal Information Security Management Act (2002; FTE+contractors = full-time equivalent (staff) plus contractors; FTEs = full-time equivalents (staff positions); GIMS = Genotyping Information Management System (TB GIMS, CDC); HIV = human immunodeficiency virus; HL7 = Health Level Seven (standards for exchanging health data); IBM = individual-based model; ICF = intensified case finding; ID = Improving Diagnosis of TB in People Living with HIV (study); INH = isoniazid; KE = Kenya; KH = Cambodia; LJ = Löwenstein–Jensen (egg-based solid culture medium for mycobacteria); LN = lymph node; LNA = lymph node aspirate; LTBI = latent tuberculosis infection; MDR = multidrug-resistant (tuberculosis); MedDRA = Medical Dictionary for Regulatory Activities; MGIT = Mycobacteria Growth Indicator Tube (liquid culture system); Modernization Act 2014); HIPAA = Health Insurance Portability and Accountability Act (1996); Mtb = Mycobacterium tuberculosis (the bacterium that causes TB); NTIP = National Tuberculosis Indicators Project (CDC); NTM = nontuberculous mycobacteria; NTSS = National Tuberculosis Surveillance System (CDC); PETTS = Preserving Effective TB Treatment Study; PHI = protected health information; PII = personally identifiable information; QA = quality assurance; QC = quality control; RPT = rifapentine; S28 = TBTC Study 28 (moxifloxacin vs isoniazid in the intensive phase of TB treatment); SQL = Structured Query Language; TB = tuberculosis; TBESC = Tuberculosis Epidemiologic Studies Consortium (CDC); TBTC = Tuberculosis Trials Consortium (CDC-sponsored); TH = Thailand; US = United States; USB = US-born; VN = Vietnam; WHODD = WHO Drug Dictionary; Xpert = Xpert MTB/RIF (Cepheid GeneXpert cartridge nucleic acid amplification test for TB and rifampicin resistance); ZN = Ziehl–Neelsen (acid-fast stain for smear microscopy).

References, compiled for this page

Full citations, with current links, for selected references and related works.

Full references: whole site, by domain (opens in a new tab) · whole site, by type of work (opens in a new tab)

Related works, not cited