This wiki has undergone a migration to Confluence found Here

Difference between revisions of "2016 08 Argonaut Provider Directory Connectathon 1"

From HL7 Argonaut Project Wiki
Jump to navigation Jump to search
(correct spelling of Endpoint)
Line 30: Line 30:
  
 
==Scenarios==
 
==Scenarios==
 +
TODO: Add example API calls
 
<!-- What will be the actions performed by participants? -->
 
<!-- What will be the actions performed by participants? -->
 
===1 Practitioner Search - Locate telecom===
 
===1 Practitioner Search - Locate telecom===

Revision as of 20:33, 8 August 2016

Back to Argonaut Implementation Guide

Background for Provider Directory

This page summarizes the requirements for a virtual provider directory connectathon August 12, 2016 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

Specification Page(s):

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

Expected participants

See the participation tracker

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

TODO: Add example API calls

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

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

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

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

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

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: