HL7AU - FHIR WG : Meeting SM TWG 2018-09-06

06 Sep 2018

Attendees

PA QA clean-up
Proposal constrain HealthcareService.location 1..1 in PD spec (wait for objections settle this week)
Search by Endpoint.identifier required api PM/LP - good suggestion; review and settle next time
VDI - V2 usage; Brett check with Jared
(PM) require support for endpoint identifier search (direct lookup of endpoint)
(JC) au receiving facility usage - discussion and outcome (multiple endpoints)
(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)

Proposal: constrain HealthcareService.location 1..1 in PD spec BE/JD 11-0-0
Proposal: Search by Endpoint.identifier included in spec PM/JD 11-0-0
VDI example
identifier": [
{
"type": {
"coding": [
{
"system": "http://hl7.org.au/fhir/v2/0203",
"code": "VDI",
"display": "Vendor Directory Identifier"
}
],
"text": "NHSD Site Service ID - Legacy"
},
"system": "http://fhir.nhsd.com.au/CodeSystem/nhsdIdentifiers#ssid",
"value": "86289",
"assigner": {
"display": "National Health Services Directory"
}
}
],
directory usage sequence Secure Message Delivery POC
appropriate approach for receiving facility usage
- Endpoint connection-type + payload-type Extensible
- multiple Endpoints needed for different receiving facilities
- see https://chat.fhir.org/#narrow/stream/18-australia/topic/Problem.20with.20au-receivingfacility.20extension