This wiki has undergone a migration to Confluence found Here
Difference between revisions of "201801 Patient Match"
Jump to navigation
Jump to search
(Created page with " Jan 2018 Proposals __NOTOC__ =Patient Match= ==Submitting WG/Project/Implementer Group== Patient Administration ==Just...") |
|||
| Line 26: | Line 26: | ||
<!-- What will be the actions performed by participants? --> | <!-- What will be the actions performed by participants? --> | ||
| − | ===Scenario | + | ===Scenario: Match existing patient resource (same server)=== |
| − | :Action: | + | :Action: Search for an existing patient using an entire patient resource from the same server |
| − | :Precondition: | + | :Precondition: A patient record exists on the server |
| − | :Success Criteria: | + | :Success Criteria: Only that patient record is returned |
| − | :Bonus point: | + | :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)== | ==TestScript(s)== | ||
Revision as of 01:51, 2 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
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
