Attendees
Agenda
- Updated sequence including search examples and usage of content guidance wrt HL7 V2 and SM elements http://build.fhir.org/ig/hl7au/au-fhir-pd/guidance.html#provider-directory-usage-sequence-for-secure-messaging
- Explicit security connection options - only have required content statement for federation nothing about client or any compliance points - can we add some?
"Any details required to authenticate to the server e.g. API key (simple fixed value), authorization header (fixed/long living bearer token), client ID/secret (OAuth details)" - Decision on finalising content - cover the following items or complete as is now. Base profile QA
- (BP) location proximity searching; R4 pre-adopt; discuss
- (PM) support for _has search parameter e.g.
[base]/HealthcareService?active=true&endpoint.payload-type=http://hl7.org.au/fhir/CodeSystem/endpoint-payload-type|http://ns.hl7.org.au/hl7v2/profiles/HL7AU-OO-REF-SIMPLIFIED-201706-L1&endpoint.status=active&_include=HealthcareService:endpoint&_has:PractitionerRole:service:identifier=http://ns.electronichealth.net.au/id/medicare-provider-number|444455AA&_has:PractitionerRole:service:active=true - (PM) Proposal PractitionerRole.healthcareService
- is useful as mustSupport so can get to service information
- (PM) could support _include healthcareservice with practitionerrole
- (KM) seek clarification on the purpose of location.managingOrganisation. According to the base spec, it is “Organization responsible for provisioning and upkeep” – which seems to me like the building owner or building manager. NHSD want to know the organisation responsible for the creation and maintenance of the location information (resource) in the directory. Where should this be recorded?(KM)
- Test Suite
- Other Business
Minutes
- Sequence diagram - more work to do
- suggest split of HL7 V2 producer and SM sender
- SM intermediary search
- Securing API
- will defer this to define a set of useful methods
- look into common usage and requirements there
- Branch - cleanup and sequence diagram; branch for snapshot (est. Oct); further work items in the current build
Action items
- BE: endpoints connection-type + payload-type Extensible
- BE: verify all searches in are covered
- BE: Search by Endpoint.identifier included in spec
- BE: HealthcareService.location 1..1 in PD spec
- BE: follow up on other territories for the states ValueSet not needed at this stage
- BE: tracker on core HealthcareService description on scope
- BP/PM: PractiitionerRole.healthcareService and _include - TH action to document the case
- BP moving SMD workflow from confluence to IG
- BE use status/active on all profiles and support search by status
