Difference between revisions of "VerificationResult FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
(migrate to Confluence)
 
(2 intermediate revisions by one other user not shown)
Line 1: Line 1:
  
 
<div class="messagebox cleanup metadata">
 
<div class="messagebox cleanup metadata">
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
+
Current version: https://confluence.hl7.org/display/FHIR/VerificationResult+FHIR+Resource+Proposal<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="background:#F0F0F0">
 
<div style="background:#F0F0F0">
 
This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
 
This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
Line 15: Line 15:
  
 
==Committee Approval Date:==
 
==Committee Approval Date:==
<i>Please enter the date that the committee approved this Resource proposal</i>
+
7 Feb 2018 (Brian Postlethwaite, Louis Bedor 3-0-0)
  
 
==Contributing or Reviewing Work Groups==
 
==Contributing or Reviewing Work Groups==
* Seeking interested workgroups
+
 
 +
*Seeking interested workgroups
  
 
==FHIR Resource Development Project Insight ID==
 
==FHIR Resource Development Project Insight ID==
Line 31: Line 32:
 
It was considered to be implemented as a profile on Provenance, however this seems to be different in scope in that its includes details of the verification.
 
It was considered to be implemented as a profile on Provenance, however this seems to be different in scope in that its includes details of the verification.
  
<!-- Define the full scope of coverage for the resource.  The scope must be clearly delineated such that it does not overlap with any other existing or expected resource.  The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%"
+
(A similar concept exists outside of healthcare in Art/Musical Equipment in Appraisals vs Provenance, the provenance of the piece covers its chain of ownership, where an appraisal covers how it was check for its authenticity)
 
 
Scope should consider numerous aspects of breadth of scope, including:
 
* Subject: Human vs. non-human vs. non-patient (e.g. lab bench medicine)
 
* Disciplines: Environmental Health, Palliative, Respiratory, Psychology, Maternity, Clinical Research
 
* Delivery environment (Community, Geriatric, Home care, Emergency, Inpatient, Intensive, Neonatal, Pediatric, Primary)
 
* Locale: Country, region
 
 
 
As a rule, resources should encompass all of these aspects.
 
-->
 
  
 
==RIM scope==
 
==RIM scope==
Line 75: Line 67:
  
 
==Example Scenarios==
 
==Example Scenarios==
* Centralized Healthcare Directory service
+
 
* Distributed/Federated Provider Directory service
+
*Centralized Healthcare Directory service
* Aggregated Directory Service
+
*Distributed/Federated Provider Directory service
 +
*Aggregated Directory Service
  
 
==Resource Relationships==
 
==Resource Relationships==
 
Reference(any) - Our initial requirements are needed against:
 
Reference(any) - Our initial requirements are needed against:
* Organization
+
 
* OrganizationRole (OrganizationAffiliation)
+
*Organization
* Location
+
*OrganizationRole (OrganizationAffiliation)
* Practitioner
+
*Location
* PractitionerRole
+
*Practitioner
* HealthcareService
+
*PractitionerRole
 +
*HealthcareService
  
 
We do not currently expect other resources to specifically reference VerificationResult
 
We do not currently expect other resources to specifically reference VerificationResult
Line 94: Line 88:
  
 
==gForge Users==
 
==gForge Users==
* brian_pos
+
 
* Cooper Thompson
+
*brian_pos
* Andrew Torres
+
*Cooper Thompson
 +
*Andrew Torres
  
 
==When Resource Proposal Is Complete==
 
==When Resource Proposal Is Complete==

Latest revision as of 15:32, 31 October 2019

VerificationResult

Owning work group name

Patient Administration

Committee Approval Date:

7 Feb 2018 (Brian Postlethwaite, Louis Bedor 3-0-0)

Contributing or Reviewing Work Groups

  • Seeking interested workgroups

FHIR Resource Development Project Insight ID

1345

Scope of coverage

The VerificationResult resource records the details and results of a resource that needs to be, or has been verified by multiple parties. It does not represent the workflows or tasks related, but does cover the who did what when, why, and when it needs to be done again.

This is in contrast to the AuditEvent which could record that a resource was received from someone, and the Provenance that records who it came from.

It was considered to be implemented as a profile on Provenance, however this seems to be different in scope in that its includes details of the verification.

(A similar concept exists outside of healthcare in Art/Musical Equipment in Appraisals vs Provenance, the provenance of the piece covers its chain of ownership, where an appraisal covers how it was check for its authenticity)

RIM scope

unknown

Resource appropriateness

When receiving content from a 3rd party system (such as a directory) it is important to be able to determine the quality of that data. This resource provides a receiver of the content the knowledge of where the data came from (especially where content was aggregated from multiple sources)

This is to be stored external to the resource, instead of within it, so that where not required, the additional content of the verification (which could be quite extensive) does not need to be loaded.


Expected implementations

The ONC has indicated that they desire to create a service that uses this capability where they will be distributing aggregated healthcare directory data from a central service to Organizations for local usage (based on a specific data usage agreement)


Content sources

Example Scenarios

  • Centralized Healthcare Directory service
  • Distributed/Federated Provider Directory service
  • Aggregated Directory Service

Resource Relationships

Reference(any) - Our initial requirements are needed against:

  • Organization
  • OrganizationRole (OrganizationAffiliation)
  • Location
  • Practitioner
  • PractitionerRole
  • HealthcareService

We do not currently expect other resources to specifically reference VerificationResult

Timelines

May Ballot 2018 - draft is in the build that went to the Jan 2018 Comment ballot

gForge Users

  • brian_pos
  • Cooper Thompson
  • Andrew Torres

When Resource Proposal Is Complete

When you have completed your proposal, please send an email to FMGcontact@HL7.org

FMG Notes