Checklist: buying health IT with HHS grant funds under the 2 CFR 200 procurement standards
Fourteen steps for health centers, hospitals and health departments spending HHS awards on software, equipment and IT services, from thresholds and specifications to sole-source limits, cost analysis and the covered telecommunications ban, as HHS has applied part 200 since October 1, 2025.
When grant money pays for health IT
Health centers, hospitals, health departments and other organizations that buy an EHR module, a telehealth platform, network equipment or IT services with an HHS grant or cooperative agreement are buying under federal procurement standards as well as their own purchasing policy. HHS adopted the government-wide Uniform Guidance at 2 CFR part 200 through an interim final rule published on October 2, 2024 (89 FR 80055) that took effect on October 1, 2025, except for one instruction effective October 1, 2024; the same rule repealed HHS’s previous regulations governing its financial assistance awards [5]. HHS’s additions now sit in 2 CFR part 300, which gives regulatory effect to part 200 for HHS awards [4]. Part 300 adds HHS-specific provisions on topics such as conflicts of interest for HHS agencies, for-profit recipients, indirect costs and research patient care costs, but none on the procurement standards themselves [4].
The procurement standards are 2 CFR 200.317 to 200.327 [1]. A separate section, 200.216, bars spending grant funds on certain telecommunications and video surveillance equipment and services [2]. On May 29, 2026 OMB and the grant-making agencies, HHS among them, proposed revising the Uniform Guidance and the agencies’ adopting rules (91 FR 32198); comments were due July 13, 2026 [6]. As checked on November 14, 2026, we found no final rule, and the text below is the current eCFR text [1] [6].
Reading the steps
Section 200.317 sends states and Indian Tribes to their own procurement policies plus sections 200.321, 200.322, 200.323 and 200.327; every other recipient and subrecipient, including subrecipients of a state, follows 200.318 to 200.327 [1]. The steps below are written for that second group. Where a step, or part of one, is our suggestion rather than a requirement, it says so. The owner under each step is a typical role, not one the rule names. Dollar thresholds that part 200 takes from the Federal Acquisition Regulation are not repeated here, because the rule points to the FAR rather than stating them [3]. This checklist explains the rules; it is not legal advice, and the terms of each notice of award also apply.
Moraph’s teams help organizations with work like this. See our solutions.
The checklist
Tick the steps as you go. The ticks are kept in this browser only; nothing is sent to us.
Procurement director
Section 200.318(a) requires documented procurement procedures consistent with state, local and tribal law and 200.317 to 200.327. Section 200.319(d) requires written procedures ensuring every solicitation describes the technical requirements clearly and states the evaluation factors [1].
General counsel with compliance
Section 200.318(c)(1) bars anyone with a real or apparent conflict from taking part in selection, award or administration and bars soliciting or accepting gratuities, with room for nominal unsolicited gifts. Section 200.318(c)(2) requires organizational conflict standards where a recipient has a parent, affiliate or subsidiary that is not a state, local government or Tribe [1]. Checking this before an affiliated IT or management company bids is our suggestion.
Chief financial officer
Section 200.320(a)(1)(iii) to (v) makes the recipient responsible for a documented micro-purchase threshold; it may self-certify up to $50,000 annually with a justification and support such as low-risk auditee status or an annual risk assessment, and needs approval from its cognizant agency for indirect costs above $50,000. Section 200.320(a)(2)(ii) says the simplified acquisition threshold may be lower than, but not above, the FAR threshold [1]. Section 200.1 defines both thresholds by reference to 48 CFR part 2, subpart 2.1 [3].
IT finance lead
Section 200.318(d) requires procedures that avoid unnecessary or duplicative items and says a lease-versus-purchase analysis should be made when appropriate [1]. Applying the same check to subscription software, by looking at what existing licenses already cover before buying, is our suggestion.
Clinical informatics or IT project lead
Section 200.319(b) requires excluding contractors that develop or draft specifications, requirements, statements of work or invitations for bids. Section 200.319(c)(6) lists specifying only a brand name product among the situations that may restrict competition, and 200.319(d)(2) allows a brand name or equivalent description when a clear description of the technical requirements is impractical or uneconomical, with the named brand’s features clearly stated [1]. A consultant that helped scope an EHR or network project and then wants to bid on it is our example of where this applies.
Procurement director
Section 200.320(a) allows micro-purchases without quotes where the price is documented as reasonable, and requires quotes from an adequate number of qualified sources for simplified acquisitions. Section 200.320(b) requires formal, competitive methods with public notice above the threshold; for proposals, all evaluation factors and their relative importance must be identified and there must be written procedures for technical evaluation and selection [1].
Procurement director with grants manager
Section 200.320(c) limits noncompetitive procurement to purchases within the micro-purchase threshold, a single source, a public exigency or emergency, written approval from the federal agency or pass-through entity, or inadequate competition after soliciting several sources [1]. For add-on modules to an installed EHR claimed as single source, recording the evidence that no other source can meet the need is our suggestion.
IT finance lead
Section 200.324(a) requires the analysis above the threshold and independent estimates before receiving bids or proposals; 200.324(c) bars cost-plus-a-percentage-of-cost contracting [1].
Procurement director
Section 200.318(h) requires considering contractor integrity, public policy compliance, proper classification of employees, past performance and financial and technical resources. Section 200.318(j) allows time-and-materials contracts only after determining no other type is suitable, with a ceiling the contractor exceeds at its own risk and a high degree of oversight [1]. Checking hourly-priced implementation and integration services against these ceiling and oversight terms is our suggestion.
IT infrastructure lead with procurement
Section 200.216(a) prohibits using grant or loan funds to procure, extend or renew contracts for covered telecommunications equipment or services, which 200.216(b), following section 889 of Public Law 115-232, defines by named manufacturers and their subsidiaries and affiliates and by entities the Secretary of Defense, in consultation with the Director of National Intelligence or the FBI Director, reasonably believes to be owned or controlled by, or otherwise connected to, the government of a covered foreign country; 200.216(c) extends this to systems that use such equipment as a substantial or essential component [2].
Contracts manager
Section 200.327 requires the applicable provisions in Appendix II to part 200. Section 200.322(a) asks recipients to prefer goods produced in the United States to the greatest extent practicable and requires the section’s requirements to be included in all subawards, contracts and purchase orders. Section 200.321 asks recipients to consider small, minority, women-owned and veteran-owned businesses and labor surplus area firms [1].
Grants manager
Section 200.318(i) sets the record contents. Section 200.325 lets the federal agency or pass-through entity review technical specifications and, when requested, pre-procurement documents, for example where a purchase above the threshold names a brand or is awarded without competition. Section 200.318(b) requires oversight of contractor performance [1]. Keeping the file with the grant records, so an auditor or program officer can follow each purchase without asking procurement, is our suggestion.
Grants compliance lead
The proposal (91 FR 32198, May 29, 2026) covers 2 CFR part 200 and HHS’s part 300, and OMB says it would also reduce recipient burden and clarify the regulatory status of the OMB requirements [6]. Until a final rule is published, the current text applies; the effective date of any change will come from the final rule, not from this page. Tracking the proposal is our suggestion.
Spotted an error? Tell us and we will check it and correct the checklist where needed.