CEM RFP Questions That Expose Closed Platforms

2 min read

Friendly RFP answers hide closed platforms. Use these questions on identity, APIs, site partners, and accreditation evidence to force concrete commitments.

An RFP can hide a closed platform behind friendly answers. “Integrations available,” “supports SSO,” and “API on roadmap” all sound fine until implementation.

If you want clinical education software that fits your campus and hospital partners, ask questions that force concrete answers.

Identity and access

  1. Which identity protocols do you support today (SAML, OIDC), and which IdPs are documented in production?
  2. Do you support SCIM for automated provisioning and deprovisioning, or only manual user admin?
  3. Can AI features be disabled by institution policy when required?

Vague “SSO available” answers are not enough. Ask for the protocol and the provisioning path.

Data movement and interoperability

  1. Is there a public, versioned API with documentation your IT team can read without an NDA?
  2. Do you support webhooks (or equivalent change notifications), or only overnight exports?
  3. Can clinical site partners get scoped access limited to their locations, without institution-wide credentials?
  4. How do programs land clinical education data in existing reporting tools (for example Power BI) or a campus warehouse?

Score the path that exists today. Roadmaps are not interfaces.

Placements and clinical partners

  1. How do hospitals receive who is scheduled and whether students are cleared without adopting another portal?
  2. Can partners update unit capacity from their own scheduling tools?
  3. What stays with the school (assignment, student detail) versus what the site can see?

If every answer routes partners into “log into our portal,” you are buying a silo with better UI.

Competency, accreditation, and evidence

  1. How does the platform connect clinical logs, skills, and evaluations to curriculum objectives and program outcomes?
  2. What evidence can leadership export for CCNE, ACEN, or allied health accreditors without rebuilding binders by hand?
  3. Which assessment workflows reduce faculty grading load while preserving educator oversight?

Ask for a workflow demo on your standards, not a generic analytics screenshot.

Implementation reality

  1. What does a 90-day pilot prove, and which success metrics do you recommend?
  2. Which parts of go-live require professional services versus admin configuration?
  3. How do you handle multi-program or multi-campus setups under one institution?

How to use the answers

Treat interoperability and evidence as scored requirements, not appendix items. A platform that wins on placements UI but fails identity, partner sync, and accreditation evidence will recreate your current spreadsheet problem inside a nicer login.

For a structured capability baseline across vendors, use the CEM Benchmark. For the HealthTasks posture on open interfaces, start with The Open CEM.