Attendees
Agenda
- Further updated sequence http://build.fhir.org/ig/hl7au/au-fhir-pd/guidance.html#provider-directory-usage-sequence-for-secure-messaging
- Base profile status
- HealthcareService
- (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
- RD: HealthcareService.type - will look at NHSD type valueset; liaise to find gap; get NCTS team to provide estimate of additions + publish as SNOMED-CT AU valueset
- RD/PW - NASH - from website rather than mail; HI service will support NASH certs rather than old medicare certs. SHA-1 → SHA-2 change; includes CSP
Action items
- BE: Sequence diagram: suggest split of HL7 V2 producer and SM sender
- 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
