Difference between revisions of "201801 Patient Match"

From HL7Wiki
Jump to navigation Jump to search
(Created page with " Jan 2018 Proposals __NOTOC__ =Patient Match= ==Submitting WG/Project/Implementer Group== Patient Administration ==Just...")
 
 
(2 intermediate revisions by the same user not shown)
Line 15: Line 15:
 
==Expected participants==
 
==Expected participants==
 
* Telstra Health
 
* Telstra Health
 +
* Epic (under consideration)
  
 
==Roles==
 
==Roles==
 
===Patient Match Server===
 
===Patient Match Server===
A server that implements the $match operation
+
A server that implements the [http://hl7.org/fhir/patient-operations.html#match $match] operation
  
 
===Patient Match Client===
 
===Patient Match Client===
Line 26: Line 27:
 
<!-- What will be the actions performed by participants? -->
 
<!-- What will be the actions performed by participants? -->
  
===Scenario Step 1 Name===
+
===Scenario: Match existing patient resource (same server)===
:Action: <!--Who does what?  (Use the role names listed above when referring to the participants -->
+
:Action: Search for an existing patient using an entire patient resource from the same server
:Precondition: <!-- What setup is required prior to executing this step? -->
+
:Precondition: A patient record exists on the server
:Success Criteria: <!-- How will the participants know if the test was successful? -->
+
:Success Criteria: Only that patient record is returned
:Bonus point: <!-- Any additional complexity to make the scenario more challenging -->
+
:Bonus point: no other patient resources are returned
 +
:Bonus point: a confidence weighting of 1.0 is returned
  
<!-- Provide a description of each task -->
+
===Scenario: Match existing patient resource (remote server)===
 +
''This could be done in cases where importing external content, and trying to locate the patient record
 +
:Action: Search for an existing patient using an entire patient resource from a different server
 +
:Precondition: A patient record exists on the server representing the same person
 +
:Success Criteria: The patient is returned in the results
 +
 
 +
===Scenario: Match partial patient resource ===
 +
''This is likely to be done from patient search screens on EHRs
 +
:Action: Search for an existing patient using a partially populated patient resource constructed from the search parameters on the display
 +
:Precondition: Patient record(s) exist on the server that could match the details
 +
:Success Criteria: Appropriate patient matching results provided
 +
:Bonus point: confidence weighting is included with the results
  
 
==TestScript(s)==
 
==TestScript(s)==

Latest revision as of 21:23, 8 November 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
  • Epic (under consideration)

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: Match existing patient resource (same server)

Action: Search for an existing patient using an entire patient resource from the same server
Precondition: A patient record exists on the server
Success Criteria: Only that patient record is returned
Bonus point: no other patient resources are returned
Bonus point: a confidence weighting of 1.0 is returned

Scenario: Match existing patient resource (remote server)

This could be done in cases where importing external content, and trying to locate the patient record

Action: Search for an existing patient using an entire patient resource from a different server
Precondition: A patient record exists on the server representing the same person
Success Criteria: The patient is returned in the results

Scenario: Match partial patient resource

This is likely to be done from patient search screens on EHRs

Action: Search for an existing patient using a partially populated patient resource constructed from the search parameters on the display
Precondition: Patient record(s) exist on the server that could match the details
Success Criteria: Appropriate patient matching results provided
Bonus point: confidence weighting is included with the results

TestScript(s)

Security and Privacy Considerations