2016 08 Argonaut Provider Directory Connectathon 1

From HL7 Argonaut Project Wiki
Jump to navigation Jump to search

Back to Argonaut Implementation Guide

Background for Provider Directory

This page summarizes the requirements for a virtual provider directory connectathon August 12, 2016 from 12-5PM ET based on Argonaut PD

Location

Virtual! We will use gotomeeting for screen sharing and Zulip for group chat.

  • Please register for the gotomeeting here
  • The Zulip stream is available here

Expected participants

See the Participation Tracker

Specification Page(s):

We plan to provide feedback to HL7 on the new Endpoint resource.

Roles

Provider Directory Server

A Server with Provider directory data

Provider or Patient Consumer search application

An application used by a user to search for information on a specific provider or organization.

Scenarios

1 Practitioner Search - Locate telecom

Action: Locate a Practitioner's telecom and physical address
Precondition: FHIR Practitioner on the server
Success Criteria: The desired resources were found
Example Searches
  • GET [base]/Practitioner?identifier=[system]|[code]
  • http://fhirtest.uhn.ca/baseDstu3/Practitioner?identifier=http://hl7.org.fhir/sid/us-npi|9941339108
  • GET [base]/Practitioner?family=[string]&given=[string]
  • http://api.sandboxcernerdirect.com/hpd-service/api2/Practitioner?given=greg&family=stella
  • GET [base]/Practitioner?specialty=[system]|[code]
  • GET http://fhirtest.uhn.ca/baseDstu3/Practitioner?specialty=207RS0010X

2 Practitioner Search - Locate Direct address

Action: Locate a Practitioner's Direct address
Precondition: FHIR Practitioner and Endpoint
Success Criteria: The desired resources were found
Bonus point: The criteria for the resources used several restrictions, possibly Specialty or Location
Example Searches
Same as in Scenario 1 except retrieve direct address. See the participation tracker to see which servers support direct address.
  • GET [base]/Practitioner?given=[name]&_include=Practitioner:endpoint
  • http://api.sandboxcernerdirect.com/hpd-service/api2/Practitioner?given=greg&_include=Practitioner:endpoint
Practitioner Resource Example with EndPoint 

3 Organization Search - Locate Endpoint

Action: Locate an Organization's Endpoint
Precondition: FHIR Organization and Endpoint
Success Criteria: The desired resources were found
Bonus point: The criteria for the resources used a Location restriction
Example Searches
  • GET [base]/Organization?identifier=[system]|[code]
  • http://fhir3.healthintersections.com.au/open/Organization?identifier=urn:ietf:rfc:3986|2.16.840.1.113883.19.5
  • GET [base]/Organization?name=[string]
  • http://fhirtest.uhn.ca/baseDstu3/Organization?name=good

...now if only these had endpoint included :)

Organization Resource Example with EndPoint 

4 Location Search - Locate telecom

Action: Locate a Location's telecom and physical address
Precondition: FHIR Location on the server
Success Criteria: The desired resources were found
Example Searches
  • GET [base]/Location?name=[string]
  • https://open-ic.epic.com/FHIR-2016/api/FHIR/Connectathon/Location?name=EHS
  • GET [base]/Location?address=[string]
  • http://wildfhir.aegis.net/fhir/Location?address=Ann Arbor

5 Location Search - Locate Endpoint

Action: Locate a Location's Endpoint
Precondition: FHIR Location and Endpoint
Success Criteria: The desired resources were found
Bonus point: The criteria for the resources using an Organization restriction
Location Resource Example with EndPoint

6 Search by Organizational relationships

Action: Search for a Practitioner in a specific organization, retrieve Direct address
Precondition: FHIR Practitioner, Organization and Endpoint
Success Criteria: Successful retrieval of Practitioner's Endpoint for a specific organization
Bonus point:
Example Searches
  • GET [base]/Practitioner?organization:
  • http://api.sandboxcernerdirect.com/hpd-service/api2/Practitioner?organization:address=hudson

Baltimore PD Connectathon