Multidisciplinary Team Conference Note (Developmental-Behavioral Pediatrics)
Documents multidisciplinary team conferences in developmental-behavioral pediatrics, synthesizing data from medical, school, and therapy sources into consensus impressions and a coordinated plan with assigned responsibil…
Document Type
clinical note / Consultation Note
Specialties
Template Preview
Patient: [Name and identifiers]
DOB: [Date of birth]
Conference Date: [Date]
Encounter Type: Multidisciplinary Team Conference (DBP)
Modality: [in-person / video / phone / asynchronous review]
Primary Topic(s): [Brief focus of conference] (Summarize core purpose such as diagnostic clarification, school supports alignment, or treatment adjustment.)
Conference Participants
- [Name], [Credentials] — [Discipline/Role] — [attended live / reviewed materials only]
- [Name], [Credentials] — [Discipline/Role] — [attended live / reviewed materials only]
- [Family member name or relation] — [participated live / reviewed summary / not present] (Only include if explicitly involved.)
Facilitator: [Name, Credentials]
Reason for Conference
[Trigger and specific clinical questions] (In 1–3 sentences, state why the team met and the concrete questions being addressed. Avoid vague statements like "review case." Examples: new evaluation data to interpret, diagnostic uncertainty, school-clinic alignment needs, treatment plateau requiring coordinated adjustment.)
Data Sources Reviewed
(Summarize high-yield information that informed discussion. Include document/test name, date, source, and brief key findings with quantitative results where available. Note explicitly if critical data were unavailable or pending.)
Medical/Clinic Records
- [Document/test name], [Date], [Author/Service] — [Key findings with quantitative results if available]
School Records
- [IEP/504/psychoeducational assessment/teacher report], [Date], [Source] — [Primary findings: eligibility, cognitive/achievement results with ranges, classroom observations]
Therapy Records
- [Service type], [Date range], [Provider/Agency] — [Goals, frequency, progress, objective measures]
Standardized Rating Scales
- [Instrument], [Informant], [Date] — [Score(s) with clinical range/percentile and interpretation]
Case Summary
(Provide a concise problem representation with only details necessary to interpret the reviewed data.)
- [Age], [Grade], [Educational placement]
- [Known diagnoses] and [suspected diagnoses]
- [Communication/language profile]
- [Learning/academic profile]
- [Behavior/regulation profile]
- [Adaptive/daily living skills]
- [Relevant comorbidities] (Only if they affect interpretation or plan.)
- [Current services and treatments]
- [Safety concerns] (Only if applicable.)
Team Discussion
(Summarize key discussion points. Distinguish facts from interpretation. Use neutral, behaviorally anchored language. Attribute statements to disciplines only when clarifying differing opinions or responsibilities.)
- Facts reviewed: [Objective or documented findings from reports and completed tests]
- Reported information: [Parent/teacher/clinician reports with sources attributed]
- Clinical reasoning: [Team synthesis explaining how data answer the clinical questions]
- Areas of agreement: [Consensus points and rationale]
- Conflicting data: [Discrepancies and how reconciled] (Only include if applicable.)
- Limitations: [Data gaps, validity concerns, contextual factors]
Consensus Impressions
(List in order of priority. For each, include condition/concern, diagnostic status, functional impact, and evidence basis. If diagnosis was discussed but not formally assessed during this conference, state that in-person diagnostic evaluation is required for confirmation.)
- [Condition/Concern]: [confirmed / suspected / rule-out / monitoring] — [Functional impact] — [Evidence basis from reviewed data]
- [Condition/Concern]: [status] — [Functional impact] — [Evidence basis]
Coordinated Plan and Responsibilities
(Organize by domain. Each recommendation must be actionable with responsible party, specific action, and target timeframe. Note dependencies such as ROI or authorizations when applicable.)
Medical/DBP
- Responsible: [Role/Name] — Action: [Specific task] — Timeframe: [Date/interval]
Behavioral and Mental Health
- Responsible: [Role/Name] — Action: [Therapy/behavior plan task] — Timeframe: [Date/interval]
Speech-Language
- Responsible: [Role/Name] — Action: [Evaluation/therapy task] — Timeframe: [Date/interval]
Occupational Therapy
- Responsible: [Role/Name] — Action: [Evaluation/therapy task] — Timeframe: [Date/interval]
Educational Recommendations
- Responsible: [School contact/family/clinician] — Action: [Proposed accommodations/services/goals] — Timeframe: [Target meeting date] — Dependencies: [ROI status if applicable]
Family Supports and Care Coordination
- Responsible: [Care coordinator/family/clinician] — Action: [ROI, referrals, resources] — Timeframe: [Date/interval]
Monitoring Plan
- Measure: [Rating scales/reports/logs] — Frequency: [Interval] — Responsible: [Role/Name]
(If no follow-up tasks generated, state: No new tasks assigned during this conference.)
Follow-Up
- Next appointment: [Visit type], [Timeframe], [Provider]
- Pre-visit information to obtain: [Updated rating scales / school data / therapy reports] — Responsible: [Role/Name]
- Family communication: [Method and timing for sharing recommendations if family not present]
- Written summary distribution: [Recipients and expected date] (Note ROI status for external recipients.)
Conference time: [Total minutes] — Family present: [yes / no] (Include if tracking for billing or care coordination metrics.)
(Meta-instructions: Distinguish observed/measured information from reported information from team interpretation from consensus decisions. Do not infer diagnoses or scores not explicitly reviewed. If critical data are missing, document and note which decisions were deferred. Use standard abbreviations only. Use addenda for subsequent updates rather than overwriting prior documentation.)
Want to use this template?
Copy it into your workflow, or book a demo to see Augustun draft notes like this automatically.