Proposed agenda for workshop.
10:00am – 10:30am Introduction
- Purpose: federated directories, common data modes and interfacing
- Perspectives: directory suppliers, consumers
- Resources: FHIR specification (resources, API), implementation guides (profiles)
- Tools: open source projects, validators
10:30am-11:15am Core Entity Patterns
- Core Resources – which FHIR resources are needed?
- Relationships – related entities; hierarchies and association patterns
- Which resources have endpoints?
11:15am-11:30am Break
11:30am-12:15pm Core Entity Data
- Organisation – entity data requirements, logical and physical location, role
- Practitioner – entity data requirements, individual person
- PractitionerRole – entity data requirements, person in role
- Location – entity data requirements, address, physical location
12:15pm-1:00pm Lunch
1:00pm-1:45pm Endpoint/Service/Payload
- Endpoint – information, business, and service requirements
- Certificates – by value and reference
- Service Interface – connection type (existing definitions)
- Service Category – payload scheme, payload type (existing definitions)
- Delegation – contracted service provider
1:45pm-2:30pm Interactions and Access
- Search – search criteria (by resource); required/typical capability
- Bundled results (include) – required/typical bundled results
- Directory services location – how to locate directory services
- Service authentication/authorisation methodology
- Record provenance – federated results
- Audit - access auditing requirements
2:30pm-2:45pm Break
2:45pm-3:30pm
- Discuss planned activities from the workshop
- Formalisation: Provider Directory FHIR implementation guide – publication timing
- Online participation: HL7 Australia Wiki, Instant messaging chat.fhir.me (Zulip)
- Public implementations and examples
- Review: regular review teleconferences; HL7 AU Patient Administration WG
- Next Connectathon event – implementation event, planning, timing, participation
3:30pm-4:00pm
- Next steps – further needs for this project
- Concerns and issues