This historical CHSPS news article was published in 2015 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.
What changed in 2015
The shared requirements matured into a reusable core built around controlled documents, effective dates, reviewer independence, due process, post-award maintenance and material-change handling. That common architecture allowed later program standards to add subject-specific requirements without duplicating the same governance controls.
Strengthened controlled-document ownership, edition control, effective dates and reviewer independence.
Separated complaints, appeals and reconsideration while adding post-award maintenance and material-change expectations.
2015 in context
The common requirements mature into a reusable core so future program standards can share governance, impartiality, records, appeals and monitoring controls.
This common-core approach is what allows today's portfolio to use program-specific standards without rebuilding the same governance clauses sixteen different ways.
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 2015
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.
Core requirements and document control
Strengthened controlled-document ownership, edition control, effective dates and reviewer independence.
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.
Impartiality, appeals and maintenance
Separated complaints, appeals and reconsideration while adding post-award maintenance and material-change expectations.
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 2015
The common requirements mature into a reusable core so future program standards can share governance, impartiality, records, appeals and monitoring controls.
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.
This common-core approach is what allows today's portfolio to use program-specific standards without rebuilding the same governance clauses sixteen different ways.
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 2015 coverage
Related CHSPS articles published for 2015, each tied to the year's controlled standards and program record:
- Appeals and due process — Why complaints, reconsideration and appeals need distinct controlled routes.
- Document control — How effective dates, versions and superseded records keep requirements stable.
- Maintenance after award — Why accreditation remains active work after the initial decision.
- Reviewer independence — Why case-specific conflict screening protects technical judgment.