This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "VerificationResult FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 98: Line 98:
==gForge Users==
==gForge Users==
* brian_pos
Cooper Thompson
* Cooper Thompson
Andrew Torres
* Andrew Torres
==When Resource Proposal Is Complete==
==When Resource Proposal Is Complete==

Revision as of 17:15, 2 February 2018


Owning work group name

Patient Administration

Committee Approval Date:

Please enter the date that the committee approved this Resource proposal

Contributing or Reviewing Work Groups

  • Work Group Name
  • or link
  • or "None"

FHIR Resource Development Project Insight ID


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.

RIM scope


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


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

FMG Notes