2016 11 Argonaut Provider Directory Connectathon 2

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 November 18, 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):

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 Specialty Search

Action: Locate a Provider by Specialty.
Precondition: FHIR Practitioner, PractitionerRole on the server with a specialty.
Success Criteria: The desired resources were found and a Practitioner, and EndPoint resource were returned.
Example Searches
  • GET [base]/PractitionerRole?specialty=[system]|[code]
  • GET http://fhir3.healthintersections.com.au/open/PractitionerRole?specialty=http://hl7.org/fhir/practitioner-specialty%7Ccardio
  • GET [base]/PractitionerRole?specialty:text=[specialty]
  • GET http://fhir3.healthintersections.com.au/open/PractitionerRole?specialty:text=cardio
  • Use of _include - &_include=PractitionerRole:organization&_include=PractitionerRole:endpoint 
PractitionerRole Resource Example with contained Endpoint and Practitioner
PractitionerRole_Resource_Example_with_referenced_Practitioner
PractitionerRole_Resource_Example_with_referenced_Practitioner_Endpoint

2 Provider Name Search

Action: Locate a Provider by name
Precondition: FHIR Practitioner, PractitionerRole on the server.
Success Criteria: The desired resources were found and a Practitioner, and EndPoint resource were returned.
Example Searches
  • GET [base]/PractitionerRole?practitioner.family=[string]&practitioner.given=[string]
  • GET http://fhir3.healthintersections.com.au/open/PractitionerRole?practitioner.family=verify&practitioner.given=v


3 Provider NPI Search

Action: Locate a Provider by NPI
Precondition: FHIR Practitioner, PractitionerRole on the server.
Success Criteria: The desired resources were found and a Practitioner, and EndPoint resource were returned.
Example Searches
  • GET [base]/PractitionerRole?practitioner.identifier=[system]|[code]
  • GET http://fhir3.healthintersections.com.au/open/PractitionerRole?practitioner.identifier=http://hl7.org.fhir/sid/us-npi|9941339108


4 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

5 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

6 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

7 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

San Antonio PD Connectathon

Retrieved from "https://argonautwiki.hl7.org/w/index.php?title=2016_11_Argonaut_Provider_Directory_Connectathon_2&oldid=2044"