Difference between revisions of "201801 Patient Merge"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "{{subst::Template for FHIR Connectathon Track Proposals}}")
 
Line 2: Line 2:
 
[[Category:201801_FHIR_Connectathon_Track_Proposals|Jan 2018 Proposals]]
 
[[Category:201801_FHIR_Connectathon_Track_Proposals|Jan 2018 Proposals]]
 
__NOTOC__
 
__NOTOC__
=Track Name=
+
=Patient Match=
  
 
==Submitting WG/Project/Implementer Group==
 
==Submitting WG/Project/Implementer Group==
<!-- Who is asking for this track? -->
+
Patient Administration
  
 
==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. -->
+
The Patient Match operation was updated in STU3, and implementation experience on this new definition is desired prior to going Normative in R4
  
 
==Proposed Track Lead==
 
==Proposed Track Lead==
<!-- Name, email and Skype id of individual who will coordinate the track at the connectathon -->
+
Brian Postlethwaite (skype: sgtshultzpos email: brian_pos at hotmail dot com)
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 -->
+
* Telstra Health
  
 
==Roles==
 
==Roles==
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
+
===Patient Match Server===
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
+
A server that implements the $match operation
===Role 1 Name===
+
 
<!-- Provide a description of the capabilities this role will have within the connectathon -->
+
===Patient Match Client===
 +
A client application that is able to call the match operation and view/process the results (including the weightings if included)
  
 
==Scenarios==
 
==Scenarios==

Revision as of 20:42, 25 October 2017


Patient Match

Submitting WG/Project/Implementer Group

Patient Administration

Justification

The Patient Match operation was updated in STU3, and implementation experience on this new definition is desired prior to going Normative in R4

Proposed Track Lead

Brian Postlethwaite (skype: sgtshultzpos email: brian_pos at hotmail dot com)

Expected participants

  • Telstra Health

Roles

Patient Match Server

A server that implements the $match operation

Patient Match Client

A client application that is able to call the match operation and view/process the results (including the weightings if included)

Scenarios

Scenario Step 1 Name

Action:
Precondition:
Success Criteria:
Bonus point:


TestScript(s)

Security and Privacy Considerations