Accreditation Eligibility and scope inquiries are accepted year-round. Begin with a no-fee eligibility and scope review. Start Free Eligibility Review · Current program status
Eligibility reviews open year-round · No fee Verify AccreditationContactMy CHSPS
CHSPS — Commission for Health, Safety & Professional Standards
Historical news · published 2014

2014 Standards & Program Portfolio Review

Foundational governance and public accountability.

Publication dateDecember 15, 2014
Archive year2014
PublisherCHSPS Communications
Record typeHistorical news article
December 15, 2014 Publication year: 2014 CHSPS Communications
Published December 15, 2014

This historical CHSPS news article was published in 2014 and documents the standards and program-development record presented for that year. For present requirements and status, use the current Standards Registry, Program Status and other controlling public records.

Year at a glance

What changed in 2014

CHSPS concentrated on the governance and review foundation needed before program-specific accreditation could be offered. Edition 2014.1 separated standards development, technical review and final decision authority; Edition 2014.2 tightened scope definition, evidence traceability and control of public claims.

PublishedDecember 15, 2014
Controlled editions2
Program changesShared architecture
Related coverage4 articles
Edition 2014.1
Charter, governance and decision separation

Established the baseline separation between standards development, technical review and final decision authority.

Edition 2014.2
Scope, evidence traceability and public claims

Added clearer expectations for defining scope, mapping evidence and controlling public accreditation claims.

Program-development position
No new current portfolio code assigned in this year

2014 in context

CHSPS establishes the governance, standards-development and impartial-review architecture needed before program-specific accreditation can be offered.

The year created the common operating foundation later reused by every current accreditation, certification and scope-module pathway.

The important change is not simply that another document number appears in the register. Each controlled edition represents a defined point at which requirements, scope language, evidence expectations or review controls were made more explicit. Program additions follow the same logic: a new pathway is introduced when the subject requires a distinct unit of accreditation or certification, not merely because the portfolio can support another name.

Controlled editions issued during 2014

The edition sequence below shows how the standards architecture developed during the year. The sequence is cumulative: later editions within the same year supersede the earlier controlled version while preserving the historical change record.

Edition 2014.1

Charter, governance and decision separation

Established the baseline separation between standards development, technical review and final decision authority.

The revision is part of the YYYY.N controlled-edition sequence: the year identifies the publication cycle and the number after the period identifies the sequence of controlled editions within that year. A later sequence number represents a substantive controlled revision, not a decimal software version.

Edition 2014.2

Scope, evidence traceability and public claims

Added clearer expectations for defining scope, mapping evidence and controlling public accreditation claims.

The revision is part of the YYYY.N controlled-edition sequence: the year identifies the publication cycle and the number after the period identifies the sequence of controlled editions within that year. A later sequence number represents a substantive controlled revision, not a decimal software version.

Program-development position in 2014

CHSPS establishes the governance, standards-development and impartial-review architecture needed before program-specific accreditation can be offered.

No additional current portfolio code is assigned to this year in the chronology. The work instead strengthened the common controls that later program standards rely on. That distinction matters because adding a program before its scope and evidence model are mature would make the portfolio less coherent, not more complete.

How this year connects to the current 16-code portfolio

The current CHSPS portfolio is intentionally layered. general accreditation pathways address certification programs, education providers, courses, assessment-based credentials and work-based learning. Specialty accreditations address assessment integrity, remote examinations, medication safety, workforce competency, clinical education and AI governance. Supplements, system certifications and scope modules then address narrower uses such as AI-assisted assessment, AI proctoring technology, AI learning platforms, provider AI-learning use and telehealth workforce competency.

The year created the common operating foundation later reused by every current accreditation, certification and scope-module pathway.

Evidence and decision principles carried forward

Across the chronology, four principles remain stable. First, scope has to be defined before review. Second, a requirement must be supported by controlled documentation and implementation evidence. Third, review and final decision authority must remain impartial and traceable. Fourth, a public claim must stay within the approved scope and remain independently verifiable. New program standards add subject-specific requirements, but they do not replace these core controls.

What readers should use today

Historical editions explain how the architecture developed. They do not replace the current controlled standards. Applicants and accredited organizations should use the current Standards Library, program page and written CHSPS scope confirmation for present requirements. Public status should be checked through the current verification record.

More 2014 coverage

Related CHSPS articles published for 2014, each tied to the year's controlled standards and program record:

  • Evidence traceability — How controlled evidence and reviewer notes create an auditable path to a decision.
  • Governance separation — Why standards development, technical review and final decisions need separate authority.
  • Public claims control — Why marks, seals and public descriptions must match the approved scope.
  • Scope before review — Why a defensible review begins by defining the exact program, system and exclusions.