Move reviewed feedback into your program’s workflow

PDF preserves the readable note and attribution. Attach it only where your program accepts supporting documents; uploading a PDF does not automatically populate assessment fields.

Excel keeps the existing summary sheet and adds a Fields sheet with the actual form-specific fields. CSV offers the same field rows for mapping; formula-like values are prefixed with an apostrophe for spreadsheet safety. Prefer JSON or text when exact literal values are needed.

Copy fields / text helps with manual entry into the matching form. Word and Markdown provide editable document copies. JSON is a versioned DebriefMD handoff for an administrator or future connector. None is a universal assessment-import format.

Open a reviewed debrief and choose Prepare system handoff. Preparing a handoff gives you a copy; it does not share the notes with your program in DebriefMD (use Share with program for that). Check learner, assessor, date, form version, ratings and attribution in the destination, then complete its required approval. A downloaded file is not a filing receipt.

Connections are disabled by default. A configured Canvas learner-artifact adapter and LTI Core launch verifier are available for controlled tenant acceptance; the other profiles are discovery requirements. The profiles below describe public research checked on 22 October 2026, with tenant-specific questions still open.

A vendor-published API example shows tenant client credentials, bearer tokens and form listing. Current delegated access and supported assessment writes need vendor confirmation.

The vendor import-template index lists XLSX imports. A completed-evaluation import template has not been verified; a generic CSV or XLSX is not established as compatible.

Ask the institutional keyholder for current API documentation, supported grant, assessment workflow and an accepted synthetic import template. Use reviewed copy/PDF while verifying.

• Vendor API example (updated December 2023)
• One45 import-template index (search-index evidence; article body unavailable)

Elentra documents a modular authenticated API and mobile assessment workflows. Access, modules, versions and supported third-party writes depend on the installation.

Documented CSV import populates course gradebook grades. It does not establish an importer for completed CBME/EPA narrative assessments. PDF/CSV reports are exports.

Obtain the tenant API/module inventory and supported external-assessor/distribution or assessment-write contract. Verify current form/question IDs and authorship in a sandbox.

• API architecture
• Gradebook CSV import
• Mobile implementation notes

The vendor documents API-based integration. Its myTIPreport guide demonstrates a configured completed-evaluation publishing integration.

That integration uses a dedicated locked form and linked identities. It is a partner precedent, not an open CSV/XLSX import contract for DebriefMD.

Request partner API access and a named integration form. Agree on identity mappings, immutable submission/correction rules and delivery receipts.

• MedHub integration overview
• myTIPreport evaluation publishing

The vendor explicitly offers an API and a daily Data Exchange service.

The vendor agrees file layouts and mappings for imports/exports, including evaluation session matches. Completed evaluation answers and narrative support remain unconfirmed.

Ask for the evaluation-answer object contract or agreed file layout, transport/security, row-level rejection report and destination record receipts.

• Vendor API and Data Exchange

Public APIs support assignment text/file submissions and file upload, subject to course permissions and allowed assignment submission types.

A reviewed PDF may be submitted to an assignment configured for file uploads. A gradebook CSV is not a narrative EPA assessment import.

Confirm the assignment accepts the handoff as a learner artifact. Obtain scoped OAuth developer access, course/assignment identity and upload/submission read-back tests.

• Assignment submissions API
• File upload API

Moodle provides external services with institution-configured functions and permissions. The available service/function set must be checked on the target site.

Use a reviewed PDF/text artifact only where the configured assignment permits it. Generic CSV grade import does not create a preceptor-authored EPA assessment.

Confirm assignment plugins, upload/save/submit functions, scoped service token and actor permissions on the exact Moodle version.

• External services documentation

Calgary Family Medicine documents MedSIS assessment use from July 2026; Toronto is preparing MedSIS 3C for 2027–28. A public third-party completed-assessment API contract has not been verified.

Obtain the exact tenant-approved assessment importer or attachment workflow. Do not infer an import schema from another MedSIS installation or an exported report.

Ask LGI and the institutional technical owner for the version/module inventory, delegated access, form/question identifiers and a synthetic filing round trip.

• Calgary assessment-platform transition
• Toronto MedSIS 3C implementation

The vendor describes integration and import tools for eValue. Its contract is separate from the MedHub API and must be obtained for the exact tenant.

Institution-approved layouts and workflows are needed for narrative evaluations; a generic spreadsheet is not an accepted evaluation-import contract.

Confirm the evaluation and portfolio object schemas, identity mappings, author attribution, permitted destinations and rejection/receipt reports with the vendor.

• eValue platform and integration tools

The vendor documents a configured risr/assess-to-advance results integration with event types and mapped candidate identities. This is not evidence of open DebriefMD write access.

Event types define fields and completion workflows. Obtain a supported third-party event/evidence import contract and attachment limits for the target tenant.

Request the event creation API or import schema, completing actor rules, candidate identity, correction semantics and a tenant sandbox. Do not reuse exam-result endpoints for workplace notes without approval.

• Vendor results integration and event types

DebriefMD implements configured Core resource-link launch verification with single-use state, nonce, signature, issuer, audience, deployment and browser binding. Existing DebriefMD sign-in and memberships remain required.

LTI is a launch/service protocol, not an assessment file format. Gradebook services do not by themselves represent a narrative preceptor-authored EPA.

Register the issuer/client/deployment, HTTPS initiation/launch/target URLs and approved JWKS endpoint. Test real browser cookies and existing account access. NRPS roster and AGS grade services require separate scoped implementation and tenant acceptance.

• LTI Core 1.3 specification
• LTI Advantage services

The checklist contains no credentials or assessment data. Use references to approved documentation and evidence; keep secrets in your institution’s approved secret store.

1. Tenant and owner. Exact tenant URL, institution, program scope, platform/version, named technical owner and sandbox.
2. Authorized access. Supported scoped grant or service account, secret-store reference, rotation/revocation and denied cross-program tests. Never collect an institutional password.
3. Supported destination workflow. Vendor/admin confirmation of the exact write operation or completed-assessment importer, template/schema, size limits and sandbox example. Roster, schedule or grade imports are different workflows.
4. Identity and authorship. Stable resident, assessor, program and academic-year mappings. Record DebriefMD as drafter and retain the real completing actor; never impersonate a preceptor.
5. Versioned field mapping. Frozen source form ID/definition hash and destination form/version/question IDs. Map every field and rating option explicitly; record unmapped items and preserve attribution, blanks and multi-note structure.
6. Exact reviewed revision. Bind resident release to the submitted content hash. Changes invalidate approval. Confirm any destination-required assessor approval separately.
7. Data and residency approval. Approved destination/processing locations, minimum payload, retention/deletion and institutional agreement. No audio, transcript, self-reflection or model evidence in the handoff.
8. Delivery and reconciliation. Idempotency key, timeouts/rate limits, retry policy, destination record ID and read-back receipt. A download or HTTP 200 alone is not official filing.
9. Corrections and rollback. Define draft/final states, locked-record amendments, duplicate handling, revocation and reconciliation; do not assume a submitted evaluation can be edited or deleted.
10. Tenant acceptance evidence. Synthetic end-to-end filing approved by program/admin: exact fields, authorship, receipt, denied foreign access, duplicate retry and correction. Record versions and dated evidence.

Completing a checklist starts engineering review. It does not enable a connection or certify that a platform accepts DebriefMD files.

Settings → Exports and data tools provides a reviewed portfolio ZIP, dated cohort exports for program administrators, preview/commit CSV imports, and a delivery journal. Manual filing is labelled resident-reported. API acceptance requires destination read-back; uncertain outcomes must be reconciled before a retry.

Program-specific spreadsheet and fillable PDF outputs require an approved, versioned profile pinned to both source form and PDF hashes. A missing mapping, option, source revision or text capacity blocks output. Digital signatures and assessor approval are never fabricated.

The Canvas adapter submits a learner-authored text artifact to a configured assignment, never a preceptor evaluation or grade. It refuses existing content. LTI launch requires a configured issuer and existing DebriefMD sign-in; LMS roles do not grant leadership access.