This EB-2 NIW public health evaluator had managed maternal-health outreach, chronic-disease screening, community referrals, and grant reporting for years. Her case changed when the evaluation work was reconstructed as a repeatable system that other organizations could use to measure referral completion, service reach, implementation fidelity, and corrective action.

This is an anonymized representative case study based on a completed EB-2 national interest waiver matter. Names, employers, locations, dates, program titles, partner organizations, event names, outcome figures, and selected implementation details have been withheld or adjusted to protect privacy and institutional interests.

Case at a glance

Profession	Public health program management, program evaluation, maternal and child health, chronic-disease prevention, community referral systems, and workforce training
Starting point	A master’s-trained public-health professional with approximately eleven years of experience, several successful grant-funded initiatives, strong internal reporting, limited independent recognition, and no clearly defined NIW endeavor
Expert specialization	Data-led evaluation systems for community prevention programs addressing maternal health and cardiometabolic risk
Main profile problem	The record showed that the client managed programs, but it did not identify her personal evaluation contribution, separate routine grant reporting from original work, or show that her methods could influence organizations beyond one employer
Profile-building period	Approximately eleven months before filing
What already existed	Logic models, outreach workflows, referral logs, data dictionaries, staff instructions, monthly reports, grant deliverables, corrective-action records, training slides, and supervisors and partners able to confirm the client’s role
What Advance My Profile organized or developed	A contribution chronology, a prevention-program evaluation cycle, a shared indicator dictionary, privacy-safe outcome summaries, a cohort-review method, a fidelity checklist, a corrective-action log, a practice report, professional presentations, completed peer evaluation, independent-use evidence, U.S. letters of interest, and a phased implementation plan
What was deliberately not pursued	Participant testimonials, claims that the client personally reduced maternal mortality or chronic-disease prevalence, use of restricted person-level data, authorship claims for employer-owned grant reports, a patent for routine dashboards, paid media coverage, and a broad “national public-health leader” label
Petition result	USCIS approved the Form I-140 EB-2 NIW petition without issuing a Request for Evidence

The dashboard looked complete, but it did not prove who had built the method

At intake, the client’s curriculum vitae presented a familiar public-health career. She had coordinated community screening events, trained outreach staff, monitored referrals, prepared donor reports, supported maternal-health education, and managed chronic-disease prevention activities. Her employers trusted her with complicated programs, yet the record did not explain which parts reflected her own judgment and which parts were standard requirements of a grant or job description.

Her strongest work appeared inside operating records rather than publications. Different programs collected similar information in different formats. Referral status was sometimes recorded as free text. Staff could count outreach contacts but could not always determine whether a participant reached the intended service. Monthly reports described activity, but they did not consistently show implementation fidelity, delays, incomplete follow-up, or the reasons an intervention was not working as expected.

The client had responded by designing common definitions, organizing referral stages, creating review rules, and linking program measures to corrective action. Those improvements had been used across maternal-health and cardiometabolic prevention projects. The resume reduced the work to “managed monitoring and evaluation.” That phrase concealed the actual contribution.

Legal context: USCIS Policy Manual, Volume 6, Part F, Chapter 5 explains that a petitioner must first qualify for EB-2 and then satisfy the national-interest-waiver framework. The analysis concerns the specific proposed endeavor, the person’s positioning to advance it, and whether the waiver would benefit the United States. A generally important field or occupation is not enough.

The profile audit separated routine reporting from a professional contribution

Program managers routinely prepare work plans, track budgets, collect attendance figures, answer funder questions, and submit periodic reports. We did not describe those duties as original contributions. The audit instead asked where the client had changed how a program was understood, measured, reviewed, or improved.

We reviewed dated versions of logic models, indicator sheets, referral forms, training materials, meeting notes, dashboard specifications, and corrective-action records. The chronology showed that the client had introduced a common evaluation structure after finding that several programs could report activity but could not reliably explain whether participants completed referrals, whether staff followed the intended sequence, or why performance differed among sites.

Her personal work could be traced to four decisions. She standardized operational definitions, separated reach from service completion, created a monthly cohort-review process, and required every corrective action to identify an owner, deadline, data source, and follow-up check. Supervisors and implementation partners confirmed that these changes were hers, not generic requirements copied from a funder manual.

The audit also identified a limit. The employer would not release the original dashboard, person-level records, or several internal reports. The evidence plan therefore used approved excerpts, blank templates, version histories, aggregate summaries, meeting records, and letters from people with firsthand knowledge. A proposed journal manuscript based on restricted data was not pursued because the client did not have publication rights.

The endeavor was narrowed to evaluation systems for maternal and cardiometabolic prevention

The first draft described an intention to “improve public health programs in the United States.” That statement was too broad to identify the work, users, measures, or prospective reach. It also treated public health as a subject rather than an endeavor.

The final endeavor focused on developing and implementing data-led evaluation systems for community organizations that run maternal-health and cardiometabolic-risk prevention programs. The intended users included local health departments, community health centers, maternal-health nonprofits, home-visiting and referral programs, and organizations that use community health workers or navigators.

The work did not propose clinical diagnosis, treatment, or a new medical intervention. It addressed the operating layer that allows a prevention program to define its target population, measure reach and referral completion, monitor fidelity, identify stalled cases in aggregate, compare sites responsibly, and revise delivery based on evidence.

Combining maternal health and cardiometabolic prevention required a clear boundary. The client did not claim that the two fields were interchangeable. The shared problem was program evaluation: community initiatives often need reliable definitions, referral tracking, implementation measures, and learning cycles even when the clinical subjects differ. The system was designed to preserve program-specific indicators while using a common evaluation architecture.

Technical context: CDC’s 2024 Program Evaluation Framework describes program evaluation as a structured process for understanding programs, building evidence, and improving decision-making. The case did not present the client as the author of that framework. Her contribution was an implementation method that adapted accepted evaluation principles to community prevention operations.

The prevention-program evaluation cycle made the work repeatable

We organized the client’s completed work into a six-part evaluation cycle. The cycle was not presented as a universal public-health standard. It was a documented operating model derived from her own programs and refined for use by organizations with limited evaluation staff.

Evaluation element	What the client developed	Evidence preserved
1. Program definition	A concise statement of the target population, service sequence, implementing roles, intended short-term results, exclusions, and assumptions.	Logic-model versions, work-plan annotations, approval emails, and meeting records.
2. Indicator dictionary	Shared definitions for reach, screening, referral, completed linkage, follow-up, retention, missing status, and implementation fidelity.	Dated data dictionaries, blank collection forms, code lists, and staff guidance.
3. Data-quality checks	Rules for missing fields, duplicate records, impossible dates, inconsistent referral status, late entry, and denominator changes.	Validation logs, issue summaries, dashboard specifications, and correction records.
4. Cohort review	A monthly review that grouped participants by entry period and followed aggregate progress through outreach, referral, contact, and service completion.	Review agendas, anonymized cohort tables, action notes, and partner confirmation.
5. Fidelity and barrier review	A checklist comparing intended delivery with actual delivery and recording staffing, workflow, transportation, language, technology, and partner constraints.	Fidelity forms, training records, site-comparison summaries, and corrective-action plans.
6. Learning and revision	A closed-loop process assigning each corrective action to an owner, deadline, expected evidence, and later verification.	Action registers, revised materials, follow-up reports, and implementation letters.

The cycle created a clear chain between program design, data collection, interpretation, and revision. It also showed why the client’s work was more than dashboard production. The dashboard displayed information. Her contribution defined what the information meant, how errors were handled, when a result required investigation, and how findings changed operations.

A shared indicator dictionary solved a practical comparability problem

The original programs used common words differently. One site counted a referral when staff provided a telephone number. Another counted it only after an appointment was scheduled. A third used “completed” when the participant confirmed that contact had occurred. The reports looked comparable even when they measured different events.

The client created operational definitions that separated referral offered, referral accepted, first contact attempted, contact completed, appointment scheduled, service initiated, and follow-up confirmed. She also documented who was responsible for each status, the permitted evidence, the reporting period, and how missing information would be treated.

We preserved the dated definitions and showed how they changed practice. Staff training began to use the same examples. Site reports explained denominator changes. Managers could distinguish a true service gap from incomplete documentation. External users later adapted the dictionary because it was specific enough to implement without copying the client’s employer systems.

The outcome record was useful because the claims remained limited

The available records supported operational improvement, not proof that the client had changed population-level disease outcomes. We prepared a methods note that identified the comparison periods, eligible referrals, exclusions, data-quality limits, and changes occurring at the same time.

In one adjusted example, documented referral disposition increased from approximately 64 percent to 89 percent over two reporting cycles after the common status definitions and cohort review were introduced. Median time from referral acceptance to a documented contact attempt fell from twelve days to seven days. Missing values in several required screening and follow-up fields also declined. These figures were confirmed through aggregate reports and data-custodian letters.

The petition did not claim that these changes reduced maternal mortality, prevented diabetes, lowered blood pressure, or caused better birth outcomes. The evidence showed that the evaluation system improved the organization’s ability to know who had been reached, whether referrals moved forward, where delivery failed, and what action followed. That was the contribution the records could support.

Data context: CDC lists multiple chronic-disease surveillance sources and explains that local and national data can support burden assessment, trend monitoring, and program evaluation. See Chronic Disease Data and Surveillance and PLACES: Local Data for Better Health. These public sources informed the U.S. planning approach, but they did not replace organization-specific implementation data.

Training converted the method from personal know-how into an organizational capability

The client had previously explained the dashboard during staff meetings. That was not enough to show a transferable professional product. We helped organize the completed teaching into a role-based training package for program managers, data staff, community health workers, referral coordinators, and partner organizations.

The package included a facilitator guide, sample scenarios, indicator exercises, data-quality examples, cohort-review instructions, a fidelity checklist, and short knowledge checks. Each role received only the information needed for its responsibilities. Community health workers were not expected to become evaluators, and data staff were not asked to make clinical judgments.

Attendance sheets, completed exercises, post-training questions, and revision logs showed that the materials were used and changed after feedback. The evidence was stronger than a slide deck because it recorded delivery, participation, assessment, and the specific revisions made after implementation.

Independent use showed that the system was not confined to one employer

Independent influence became the central profile-building goal. General recommendation letters could confirm that the client was competent, but they could not show that another organization had relied on her professional work.

A regional maternal-health nonprofit reviewed the blank indicator dictionary, cohort-review template, and corrective-action register. It adapted the referral-status definitions and monthly review process for two community outreach sites. The organization did not adopt every element. It retained its own maternal-health measures, changed the contact intervals, and omitted fields that were not required by its funding agreement.

A second organization, which managed cardiometabolic screening and navigation services, used the data-quality rules and fidelity checklist during a limited pilot. Its implementation letter identified the materials received, staff involved, changes made, pilot period, and observed improvement in documentation completeness. The letter did not promise permanent adoption or claim clinical results.

This partial and documented use was more persuasive than broad praise. It showed that the method could travel, that local adaptation was expected, and that the client’s contribution addressed a recurring program-management problem rather than one employer’s reporting format.

Professional authorship documented practice without taking credit for employer reports

The client had been listed as a contributor to several grant reports, but the organization owned the reports and multiple people had drafted them. We did not convert those documents into personal publications or claim sole authorship.

Instead, the client prepared a practice report on building comparable referral measures across community prevention programs. The report used no restricted data and explained the evaluation problem, operational definitions, cohort-review method, data-quality limits, and implementation lessons. It was reviewed by experienced public-health professionals before publication in a practice-oriented venue.

She also delivered a conference presentation on using cohort review to identify stalled community referrals. The presentation included a blank example and a transparent limitations section. It did not disclose the employer’s dashboard, identify participants, or suggest that the method proved clinical effectiveness.

The purpose of the writing and speaking was not to create volume. It allowed other practitioners to examine the method, created dated evidence of professional responsibility, and gave independent users a clear resource to reference.

Peer evaluation and association service showed trust in her professional judgment

Routine review of staff work inside the client’s employment was not treated as independent judging. The evidence instead used completed activities where an outside organization selected her to evaluate the work of other professionals under defined criteria.

She reviewed abstracts for a regional public health conference and later participated in a small grant-review panel for community prevention proposals. The records included invitations, reviewer instructions, conflict disclosures, completed assignments, and confirmation of service. The petition did not disclose confidential applicant material.

Her association service was similarly specific. She helped a professional working group revise a short evaluation resource for community-based programs. The evidence identified her assigned section, comments, meeting participation, and the final resource. Mere membership in the association was not used as proof of expertise.

U.S. interest was documented after organizations reviewed actual work products

We did not request generic letters stating that program evaluation is important. Potential U.S. users first reviewed the client’s blank templates, practice report, training outline, and proposed pilot sequence.

A community-health-center consortium expressed interest in testing the indicator dictionary and cohort-review method within a referral initiative serving adults with elevated cardiometabolic risk. A maternal health organization expressed interest in adapting the fidelity and corrective-action tools for a community navigation program. Each letter identified the materials reviewed, the practical problem, the anticipated internal approvals, and the limits of the interest.

The letters were not employment offers, contracts, funding commitments, or proof that a future pilot would succeed. They showed that informed organizations saw a use for the proposed work and were willing to discuss implementation under ordinary legal, privacy, and institutional requirements.

Maternal-health context: CDC’s Pregnancy Risk Assessment Monitoring System provides state, territorial, and local officials with data used to plan and review maternal and infant health programs. HRSA also describes maternal-health initiatives that combine data collection, community programs, quality improvement, and workforce support. See How We Improve Maternal Health. These sources supported the public interest context; they did not prove the client’s personal eligibility.

The U.S. implementation plan was designed for multiple organizations, not one position

The professional plan described a staged effort to help community organizations build practical evaluation systems for maternal health and cardiometabolic prevention programs. The client would work as a program evaluator, technical assistance provider, trainer, or public health program specialist within her lawful employment and contractual arrangements. She would not diagnose participants, deliver medical care, direct licensed clinical decisions, or access protected health information without authorization.

Stage	Planned work	Evidence or measure
1. Readiness assessment	Review the program theory, user roles, current forms, reporting obligations, data ownership, privacy limits, and existing public-health data.	Readiness report, data map, risk register, and approved scope.
2. Evaluation design	Co-design a logic model, indicator dictionary, data quality rules, referral stages, fidelity measures, and review calendar.	Version controlled tools, approval records, and training plan.
3. Limited pilot	Test the system with one maternal-health and one cardiometabolic-prevention organization or program unit.	Pilot logs, data completeness checks, staff feedback, and implementation notes.
4. Review and revision	Use cohort review and fidelity findings to revise definitions, forms, training, and corrective-action procedures.	Change log, revised tools, and partner confirmation.
5. Transfer and dissemination	Provide role based training, implementation guidance, and privacy-safe practice materials for additional organizations.	Training records, user requests, adoption letters, and public professional resources.

The plan identified practical measures such as data completeness, referral disposition, time to first contact, service linkage, early retention, staff adherence to the intended process, training completion, and corrective-action closure. It did not promise a reduction in mortality, disease incidence, hospitalization, or healthcare cost unless a later authorized evaluation could validly measure those outcomes.

The plan also explained how public data could support local priority setting. CDC surveillance and PLACES estimates could help characterize community needs, while PRAMS and other maternal-health sources could inform indicator selection. Local organizations would still determine the appropriate population, program design, data permissions, and interpretation.

The petition connected the record to the EB-2 threshold and each NIW prong

Immigration counsel handled eligibility analysis, legal argument, filing strategy, and submission. Advance My Profile organized the professional record, developed the evidence archive, documented completed profile-development activities, and prepared materials for counsel to evaluate. The filing kept those roles separate.

Legal issue	How the record addressed it
EB-2 eligibility	The client held a qualifying advanced degree in public health and had progressively responsible experience directly related to public health program management and evaluation.
Substantial merit	The endeavor concerned the design and implementation of evaluation systems for prevention programs serving maternal health and cardiometabolic-risk populations.
National importance	The record focused on the prospective broader implications of a transferable evaluation method that could be used by multiple community organizations, not on the importance of public health as an occupation or the benefit to one employer.
Well positioned	Dated work products, measurable operating results, independent adoption, professional authorship, presentations, peer evaluation, training, implementation experience, and informed U.S. interest showed a record of advancing similar work.
Benefit of the waiver	The proposed work was designed to cross employers and organizational settings through technical assistance, pilots, training, and dissemination. Counsel argued that tying the endeavor to one permanent job opportunity would not reflect its multi-organization structure.

The petition did not rely on a workforce shortage, a list of federal programs, or the number of people affected by chronic disease and maternal-health problems as substitutes for evidence. Those facts provided context. The filing still had to show what this client proposed to do, why the work could have broader implications, and why her record made the plan credible.

Several attractive claims were removed before filing

• The client was not described as a maternal mortality expert because she had not conducted mortality review, obstetric care, or population level mortality research.
• The petition did not claim that improved referral documentation caused better clinical outcomes.
• Employer-owned grant reports were not presented as the client’s personal publications.
• The original dashboard was not submitted because the employer had not authorized release.
• Participant stories and testimonials were excluded because they were unnecessary and raised privacy and consent concerns.
• A routine spreadsheet and dashboard were not described as patentable inventions.
• Membership fees and attendance at public-health events were not treated as independent recognition.
• Internal supervision and report review were not used as judging of the work of others.
• Letters of interest were not rewritten as contracts, funding commitments, or guaranteed pilots.
• The endeavor was not framed as a national program that the client already controlled.
• Future implementation steps were clearly identified as proposed work rather than completed achievements.
• Public health priorities were not presented as proof that every person working in the field qualifies for an NIW.
  

USCIS approved the petition without an RFE

USCIS approved the Form I-140 EB-2 NIW petition without requesting additional evidence. The decision followed a record that tied the client’s past program evaluation work to a defined prospective endeavor and showed independent use, measurable implementation, professional recognition, and informed U.S. interest.

The approval did not mean that the client had solved maternal-health or chronic-disease problems. It confirmed that the evidence satisfied the immigrant-petition classification and national-interest-waiver requirements in that matter. The professional work remained subject to employer authority, data-use agreements, privacy law, program funding, local requirements, and the limits of the client’s nonclinical role.

Form I-140 approval did not itself grant permanent residence, lawful status, employment authorization, travel permission, admission to the United States, or authority to access health data. Those matters depended on the client’s separate immigration stage and applicable legal and institutional requirements.

What professional profile advancement changed

• A broad identity as a public health program manager became a defined specialization in evaluation systems for maternal health and cardiometabolic prevention programs.
• Routine grant reporting was separated from the client’s personal work in indicator design, cohort review, fidelity monitoring, and corrective action.
• Scattered forms and reports became a dated contribution chronology supported by version histories and firsthand confirmation.
• Different referral definitions became a shared indicator dictionary that other organizations could understand and adapt.
• A dashboard became part of a larger evaluation method rather than the claimed contribution itself.
• Operational results were documented with comparison periods, denominators, exclusions, data limits, and custodian confirmation.
• Claims about disease and maternal outcomes were narrowed to what the available records could prove.
• Internal explanation became role-based training with exercises, knowledge checks, attendance, feedback, and revision records.
• Employer-confined work gained independent value after outside organizations adopted selected components and documented their use.
• Authorship arose from completed practice rather than from employer-owned reports or a publication-count strategy.
• Internal supervision was excluded, while external abstract and grant review showed completed peer evaluation.
• General support letters were replaced by informed letters from organizations that reviewed actual tools and a realistic pilot plan.
• A vague intention to improve public health became a staged U.S. endeavor with users, work products, measures, privacy boundaries, and expansion steps.
• The petition-readiness archive linked each material statement to a work product, source record, implementation event, outcome summary, or independent confirmation.
  

Lessons for public health professionals considering EB-2 NIW profile building

1.            A public health job title does not define an NIW endeavor. The work should identify a specific problem, user group, method, deliverable, and prospective reach.

2.            Program management and program evaluation overlap, but they are not identical. The record should show where the professional made decisions about definitions, measures, evidence quality, interpretation, and revision.

3.            Routine grant reports may belong to the employer or funder. Authorship and ownership should be confirmed before those documents are used as personal evidence.

4.            A dashboard is usually a display tool. The stronger contribution may be the indicator logic, data quality rules, review process, and action system behind it.

5.            Operational definitions matter. Reports cannot be compared responsibly when organizations use the same term for different events.

6.            Activity counts are not the same as outcomes. Outreach contacts, screenings, referrals, completed services, and clinical results should remain separate.

7.            Program evaluation should state the denominator, reporting period, exclusions, missing data, concurrent changes, and limits of causal interpretation.

8.            Improved documentation does not prove improved health. It may still be valuable because it allows organizations to identify gaps and manage programs more responsibly.

9.            Maternal health and chronic-disease work should not be combined only because both are important. A shared evaluation problem and clear program-specific boundaries are needed.

10.         Independent use is stronger when the adopting organization identifies the exact material, local changes, implementation period, staff involved, and limits of adoption.

11.         Partial adoption can be persuasive. A realistic letter explaining why one module was useful may be better than a broad statement claiming full replication.

12.         Training evidence should show delivery and learning, not only the existence of slides. Exercises, assessments, feedback, and revision records help establish use.

13.         Internal staff review is not automatically judging. External selection to evaluate abstracts, proposals, grants, or professional work under stated criteria is different.

14.         Public data can support local planning, but it does not replace organization-specific information, data governance, or permission to access protected records.

15.         Letters of interest should follow informed review. They should not promise employment, funding, adoption, access to data, or results that have not occurred.

16.         A strong U.S. plan identifies the organizations that could use the work, pilot sequence, resources, measures, permissions, and method of dissemination.

17.         Federal and state priorities provide context. They do not by themselves prove national importance, personal positioning, or the benefit of a waiver.

18.         Form I-140 approval is an important petition result, but it is not a green card, lawful status, work authorization, travel document, entry permission, or professional license.

Professional profile development for public-health program leaders and evaluators

Advance My Profile helps public-health program managers, evaluators, epidemiology and surveillance professionals, maternal and child health specialists, chronic-disease prevention practitioners, community-health leaders, and other professionals identify evidence hidden inside genuine work. We define defensible specializations, reconstruct contribution records, document methods and outcomes, organize ethical authorship and peer evaluation, preserve independent-use evidence, and build petition readiness archives.