Difference between revisions of "201805 Versioned API"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::Template for FHIR Connectathon Track Proposals}}")
 
Line 2: Line 2:
 
[[Category:201805_FHIR_Connectathon_Track_Proposals|May2018 Proposals]]
 
[[Category:201805_FHIR_Connectathon_Track_Proposals|May2018 Proposals]]
 
__NOTOC__
 
__NOTOC__
 +
WIP -- Work in Progress
 +
 
=Track Name=
 
=Track Name=
 +
Versioned API
  
 
==Submitting WG/Project/Implementer Group==
 
==Submitting WG/Project/Implementer Group==
<!-- Who is asking for this track? -->
+
FHIR-I + ITS
  
 
==Justification==
 
==Justification==
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. -->
+
Interest is growing in how to manage cross-version use of the FHIR API. This connectathon stream tests out 2 aspects of cross-version use of the FHIR API:
 +
 
 +
a single end-point that supports more than one version (Scenarios #1 and #2)
 +
how to handle changes a resource between versions (Scenarios #3 and #4)
  
 
==Proposed Track Lead==
 
==Proposed Track Lead==
<!-- Name, email and Skype id of individual who will coordinate the track at the connectathon -->
+
Kevin Olbrich
 
See [[Connectathon_Track_Lead_Responsibilities]]
 
See [[Connectathon_Track_Lead_Responsibilities]]
  
 
==Expected participants==
 
==Expected participants==
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
+
Kevin Olbrich (McKesson)
  
 
==Roles==
 
==Roles==

Revision as of 18:00, 2 April 2018


WIP -- Work in Progress

Track Name

Versioned API

Submitting WG/Project/Implementer Group

FHIR-I + ITS

Justification

Interest is growing in how to manage cross-version use of the FHIR API. This connectathon stream tests out 2 aspects of cross-version use of the FHIR API:

a single end-point that supports more than one version (Scenarios #1 and #2) how to handle changes a resource between versions (Scenarios #3 and #4)

Proposed Track Lead

Kevin Olbrich See Connectathon_Track_Lead_Responsibilities

Expected participants

Kevin Olbrich (McKesson)

Roles

Please include information here regarding how much advance preparation will be required if creating a client and/or server.

Role 1 Name

Scenarios

Scenario Step 1 Name

Action:
Precondition:
Success Criteria:
Bonus point:


TestScript(s)

Security and Privacy Considerations