INDUSTRY FIELD GUIDE
Multispecialty outpatient clinic task ownership data for AI
A multidisciplinary clinic may have several services using the same episode reference.
NAICS 621498 · All Other Outpatient Care Centers
A multidisciplinary clinic may have several services using the same episode reference. Census includes clinics of health practitioners with different types of credentials in this industry. HL7’s Encounter resource gives a public example of documenting care interactions. An original exercise can test which team owns an administrative action. HL7 FHIR Encounter resource · U.S. Census outpatient care scope
Create an invented episode with two service visits and a handoff that is still unassigned. Ask which team acknowledged each task and which role needs confirmation. Include one duplicate episode reference attached to a different visit.
Use dummy roles, labels and records. Exclude charts, clinician schedules, patient identifiers and internal clinic policies. Keep treatment and referral decisions outside the exercise.
Describe a fictional outpatient coordination sample
Original Fiund exercise
An episode reference can contain several visits with different task owners
A fictional clinic-coordination fixture uses role labels and administrative tasks. No clinician schedule, patient chart, internal policy or clinical referral is included.
| Record | Source | What it records |
|---|---|---|
| MV1 | Episode map | Episode E contains visit V1 for Team A and visit V2 for Team B. Task T1 belongs to V1; T2 to V2. |
| MV2 | Acknowledgments | Team A acknowledges T1/V1. Team B acknowledges T2/V2. Handoff T3 under E has owner field unassigned. |
| MV3 | Duplicate episode row | Another row repeats E but names distinct visit V3 and Team C. No T3 assignment or relationship to V1/V2 supplied. |
Question for the model
Which teams have acknowledged T1 and T2, and can T3's owner be inferred from the episode or duplicate row?
Show the reference answer and checks
MV1 and MV2 support Team A's acknowledgment of T1/V1 and Team B's of T2/V2. T3 remains unassigned in MV2. MV3's repeated episode reference and distinct V3 do not assign T3 to Team C or transfer either earlier team's acknowledgment. Preserve episode, visit and task as separate keys and request explicit ownership confirmation rather than assume every action under one episode belongs to the same team.
- Joining task ownership at episode level while ignoring visit and task IDs.
- Inferring an unassigned handoff owner from a nearby duplicate row.
Fields to preserve
- Episode, visit and task
- Defines nested identity.
- Team acknowledgment and target
- Supports the assigned action.
- Unassigned state and duplicate-row scope
- Preserves ownership gaps.
Test another case
Add a proposed T3 assignment to Team A without acknowledgment. Require proposed ownership to be distinct from accepted responsibility.
Use original dummy roles and records. Exclude charts, schedules and patient identifiers; treatment and referral decisions remain outside the task.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.