| Serial Number | 98175325 |
| Word Mark | DRUMMOND CERTIFIED |
| Filing Date | Tuesday, September 12, 2023 |
| Status | 681 - PUBLICATION/ISSUE REVIEW COMPLETE |
| Status Date | Tuesday, November 11, 2025 |
| Registration Number | 0000000 |
| Registration Date | NOT AVAILABLE |
| Mark Drawing | 3 - Illustration: Drawing or design which also includes word(s) / letter(s) / number(s) |
| Published for Opposition Date | Tuesday, December 2, 2025 |
| NOT AVAILABLE | CERTIFIED |
| Indication of Colors claimed | The color(s) gold (hex ab9257) and dark blue (hex 1e2636) is/are claimed as a feature of the mark. |
| Goods and Services | supply chain management services; healthcare services; management of information technology systems |
| Certification Mark Statement | The certification mark, as used orintended to be used by persons authorized by the certifier, certifies or isintended to certify that the goods and/or services provided have (1) met the functional requirements established under the ONC Health IT Certification Program, including conformance with specific certification criteria and test procedures approved by the Office of the National Coordinator for Health Information Technology (ONC); (2) met the security and functional requirements established by the U.S. Drug Enforcement Administration (DEA) for EPCS software, including identity proofing, authentication, audit logging, and data integrity; (3) satisfied DEA requirements for secure, electronic ordering of Schedule I-V controlled substances using PKI-based authentication and digital signatures; (4) met Drummond's interoperability, security, and reliability standards for AS2 communication, in accordance with industry expectations for secure B2B electronic data interchange (EDI); (5) met Drummond's implementation and interoperability requirements for secure AS4 messaging, including use of web service security standards; (6) met Drummond's conformance criteria for HL7 FHIR-based client applications, including secure authentication, ethical data handling, and API integration. While FHIR client certification is not federally mandated, it is becoming increasingly important as healthcare organizations prioritize seamless data exchange. The 21st Century Cures Act encourages interoperability, making it essential for client apps to align with FHIR standards. Certification helps developers and healthcare organizations demonstrate compliance with interoperability best practices and patient data security requirements; (7) met Drummond's standards for conformance testing, data handling, and interoperability with HL7 FHIR APIs. Although FHIR adoption is federally mandated, there is currently no requirement to be certified formost FHIR place potential use cases. FHIR is increasingly recognized as acritical standard for healthcare interoperability. Healthcare organizations, software developers, and regulatory bodies rely on FHIR to facilitate seamless data exchange between electronic health record systems, applications, and healthcare networks. Ensuring that systems conform to FHIR standards is essential for improving patient data accessibility and enhancing interoperability across the healthcare ecosystem; (8) met the requirements defined in the Centers for Medicare & Medicaid Services (CMS) Interoperability and Patient Access Final Rule CMS (Interoperability and Prior Authorization Final Rule CMS-0057-F), including implementation of HL7 FHIR APIs for access to claims, clinical, and authorization data; (9) met Drummond'spediatric-specific functionality criteria, ensuring electronic health record (HER) systems support safe, effective care for children. While not federally mandated, pediatric-specific HER functionalities align with recommendations from the 21st Century Cures Act and industry best practices. Pediatric-focused HER systems must demonstrate that they can facilitate safe and effective care for children, ensuring providers have the necessary tools to document and manage pediatric patient information accurately; (10) met the digital credentialing and identity verification requirements defined by the Open Credentialing Initiative (OCI), as aligned with the Drug Supply Chain Security Act (DSCSA). The Open Credentialing Initiative (OCI) establishes a standardized framework for issuing and verifying digital credentials within thepharmaceutical supply chain. OCI supports compliance with the Drug Supply ChainSecurity Act (DSCSA), which mandates secure and verifiable drug distribution processes to prevent counterfeit medications from entering the supply chain. By enabling digital verification of credentialed entities, OCI strengthens trustand security in pharmaceutical transactions; or (11) met Drummond's pDSI-Risk framework criteria for identifying and mitigating risks related to digital health solution safety, data security, and ethical AI use. While not explicitly mandated, adhering to risk assessment frameworks like pDSI-Risk is considered a best practice for healthcare organizations developing or implementing digital health solutions. Regulatory bodies and industry groups emphasize the importance of risk management in ensuring patient safety, data security, and compliance with healthcare regulations. Certification standards for all programs are attached. |
| Description of Mark | The mark consists of a white circle with a gold (hex ab9257) outline. The words DRUMMOND CERTIFIED are curved on the inside middle top of the circle in Metropolis font and dark blue color (hex 1e2636). The middle of the circle has a circular globe image that resembles a thumbprint in white and gold (hex ab9257). The inside middle bottom of the circle is used to provide specific certification program participation and sometimes the participation year or if no program is applicable is a line made up of small gold (hex ab9257) dots. |
| International Class | B - |
| US Class Codes | B |
| Class Status Code | 6 - Active |
| Class Status Date | Tuesday, October 29, 2024 |
| Primary Code | B |
| First Use Anywhere Date | Friday, April 1, 2005 |
| First Use In Commerce Date | Friday, April 1, 2005 |
| Party Name | Drummond Group LLC |
| Party Type | 10 - Original Applicant |
| Legal Entity Type | 16 - Limited Liability Company |
| Address | Durham, NC 27707 |
| Event Date | Event Description |
| Tuesday, September 12, 2023 | NEW APPLICATION ENTERED |
| Sunday, November 26, 2023 | NEW APPLICATION OFFICE SUPPLIED DATA ENTERED |
| Sunday, November 26, 2023 | NOTICE OF DESIGN SEARCH CODE E-MAILED |
| Wednesday, May 1, 2024 | ASSIGNED TO EXAMINER |
| Tuesday, May 7, 2024 | NON-FINAL ACTION WRITTEN |
| Tuesday, May 7, 2024 | NON-FINAL ACTION E-MAILED |
| Tuesday, May 7, 2024 | NOTIFICATION OF NON-FINAL ACTION E-MAILED |
| Tuesday, June 4, 2024 | TEAS RESPONSE TO OFFICE ACTION RECEIVED |
| Tuesday, June 4, 2024 | CORRESPONDENCE RECEIVED IN LAW OFFICE |
| Tuesday, June 4, 2024 | TEAS/EMAIL CORRESPONDENCE ENTERED |
| Tuesday, July 9, 2024 | NON-FINAL ACTION WRITTEN |
| Tuesday, July 9, 2024 | NON-FINAL ACTION E-MAILED |
| Tuesday, July 9, 2024 | NOTIFICATION OF NON-FINAL ACTION E-MAILED |
| Tuesday, July 30, 2024 | TEAS RESPONSE TO OFFICE ACTION RECEIVED |
| Tuesday, October 29, 2024 | ASSIGNED TO LIE |
| Tuesday, October 29, 2024 | CORRESPONDENCE RECEIVED IN LAW OFFICE |
| Tuesday, October 29, 2024 | TEAS/EMAIL CORRESPONDENCE ENTERED |
| Thursday, January 2, 2025 | NON-FINAL ACTION WRITTEN |
| Thursday, January 2, 2025 | NON-FINAL ACTION E-MAILED |
| Thursday, January 2, 2025 | NOTIFICATION OF NON-FINAL ACTION E-MAILED |
| Tuesday, April 1, 2025 | APPLICATION EXTENSION TO RESPONSE PERIOD - RECEIVED |
| Tuesday, April 1, 2025 | APPLICATION EXTENSION GRANTED/RECEIPT PROVIDED |
| Friday, June 27, 2025 | TEAS RESPONSE TO OFFICE ACTION RECEIVED |
| Friday, June 27, 2025 | CORRESPONDENCE RECEIVED IN LAW OFFICE |
| Friday, June 27, 2025 | TEAS/EMAIL CORRESPONDENCE ENTERED |
| Wednesday, August 6, 2025 | NON-FINAL ACTION WRITTEN |
| Wednesday, August 6, 2025 | NON-FINAL ACTION E-MAILED |
| Wednesday, August 6, 2025 | NOTIFICATION OF NON-FINAL ACTION E-MAILED |
| Wednesday, August 20, 2025 | TEAS RESPONSE TO OFFICE ACTION RECEIVED |
| Wednesday, August 20, 2025 | CORRESPONDENCE RECEIVED IN LAW OFFICE |
| Wednesday, August 20, 2025 | TEAS/EMAIL CORRESPONDENCE ENTERED |
| Thursday, September 25, 2025 | NON-FINAL ACTION WRITTEN |
| Thursday, September 25, 2025 | NON-FINAL ACTION E-MAILED |
| Thursday, September 25, 2025 | NOTIFICATION OF NON-FINAL ACTION E-MAILED |
| Thursday, October 30, 2025 | TEAS RESPONSE TO OFFICE ACTION RECEIVED |
| Thursday, October 30, 2025 | CORRESPONDENCE RECEIVED IN LAW OFFICE |
| Thursday, October 30, 2025 | TEAS/EMAIL CORRESPONDENCE ENTERED |
| Saturday, November 1, 2025 | APPROVED FOR PUB - PRINCIPAL REGISTER |
| Wednesday, November 26, 2025 | NOTIFICATION OF NOTICE OF PUBLICATION E-MAILED |