This wiki has undergone a migration to Confluence found Here
Difference between revisions of "DocumentSharing FHIR Profile Proposal"
Jump to navigation
Jump to search
JohnMoehrke (talk | contribs) |
(migrate to Confluence) |
||
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/DocumentSharing+FHIR+Profile+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 34: | Line 34: | ||
==Profile Details== | ==Profile Details== | ||
It is defining an IG for an ecosystem that is following the IHE White Paper on “Document Sharing”, which is the abstract model for what XDS started but has gone well beyond XDS. | It is defining an IG for an ecosystem that is following the IHE White Paper on “Document Sharing”, which is the abstract model for what XDS started but has gone well beyond XDS. | ||
− | * A document Sharing environment equally handles all kinds of documents, it is not constrained to CDA or FHIR documents. | + | |
− | * This is a working ecosystem, including patient management, patient cross referencing, User management, access controls, audit controls, provenance requirements, and eventually consent. | + | *A document Sharing environment equally handles all kinds of documents, it is not constrained to CDA or FHIR documents. |
− | * This ecosystem will be constrained following the IHE profiles, but should be able to be standalone as well. That is that it is envisioned to be equally an API to an XDS ecosystem, or deployed as a standalone Document Sharing system purely FHIR based. | + | *This is a working ecosystem, including patient management, patient cross referencing, User management, access controls, audit controls, provenance requirements, and eventually consent. |
− | * This IG will leverage existing IHE profile of the current profiles that use FHIR (MHD, PIXm, PDQm, ATNAm, and MHD-I), use of IUA, and likely future Consent profile. | + | *This ecosystem will be constrained following the IHE profiles, but should be able to be standalone as well. That is that it is envisioned to be equally an API to an XDS ecosystem, or deployed as a standalone Document Sharing system purely FHIR based. |
+ | *This IG will leverage existing IHE profile of the current profiles that use FHIR (MHD, PIXm, PDQm, ATNAm, and MHD-I), use of IUA, and likely future Consent profile. | ||
Line 43: | Line 44: | ||
<!--Put a link to the resource/datatype (or group of resources) that will be profiled here.--> | <!--Put a link to the resource/datatype (or group of resources) that will be profiled here.--> | ||
− | * DocumentReference | + | *DocumentReference |
− | * DocumentManifest | + | *DocumentManifest |
− | * List (as Document Folder) | + | *List (as Document Folder) |
− | * Patient | + | *Patient |
− | * Operation (as part of PIXm) | + | *Operation (as part of PIXm) |
− | * AuditEvent | + | *AuditEvent |
− | * ImagingObjectSelection | + | *ImagingObjectSelection |
Line 55: | Line 56: | ||
<!--Describe how the current resource will be constrained.--> | <!--Describe how the current resource will be constrained.--> | ||
− | * minor constraints as found in the profiles | + | *minor constraints as found in the profiles |
Line 61: | Line 62: | ||
<!--Describe how the current resource will be extended.--> | <!--Describe how the current resource will be extended.--> | ||
− | * None expected | + | *None expected |
Line 69: | Line 70: | ||
====As a FHIR centric Document Sharing Ecosystem==== | ====As a FHIR centric Document Sharing Ecosystem==== | ||
todo | todo | ||
− | ====As a proxy to an XDS or XCA Document Sharing Ecosystem ==== | + | ====As a proxy to an XDS or XCA Document Sharing Ecosystem==== |
todo | todo | ||
Line 97: | Line 98: | ||
<!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the Profile (optional) --> | <!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the Profile (optional) --> | ||
− | * Struct Documents | + | *Struct Documents |
− | * Imaging | + | *Imaging |
− | * PA | + | *PA |
− | * Security | + | *Security |
Line 106: | Line 107: | ||
<!--Key Profiles are justified by CCDA, for Profiles not deemed "key", what interest is there by implementers in using this particular Profile. Provide named implementations if possible - ideally provide multiple independent implementations. --> | <!--Key Profiles are justified by CCDA, for Profiles not deemed "key", what interest is there by implementers in using this particular Profile. Provide named implementations if possible - ideally provide multiple independent implementations. --> | ||
− | * much interest in IHE | + | *much interest in IHE |
− | * much interest in Argonaut | + | *much interest in Argonaut |
===gForge Users=== | ===gForge Users=== | ||
<!-- Identify the userids who will require commit access to gForge to maintain the Profile. (Ensure all users have registered for gForge.) --> | <!-- Identify the userids who will require commit access to gForge to maintain the Profile. (Ensure all users have registered for gForge.) --> | ||
− | |||
===FHIR Profile Development Project Insight ID=== | ===FHIR Profile Development Project Insight ID=== | ||
Line 130: | Line 130: | ||
Choose one: | Choose one: | ||
+ | |||
*Ballot with next FHIR DSTU or Normative Edition | *Ballot with next FHIR DSTU or Normative Edition | ||
*or Ballot independently as DSTU | *or Ballot independently as DSTU | ||
Line 137: | Line 138: | ||
<!-- Indicate the desired ballot date.--> | <!-- Indicate the desired ballot date.--> | ||
Desired Ballot Date | Desired Ballot Date | ||
+ | |||
*2016 | *2016 |
Latest revision as of 16:13, 31 October 2019
DocumentSharing
Profile balloting plans
2016
Profile Details
It is defining an IG for an ecosystem that is following the IHE White Paper on “Document Sharing”, which is the abstract model for what XDS started but has gone well beyond XDS.
- A document Sharing environment equally handles all kinds of documents, it is not constrained to CDA or FHIR documents.
- This is a working ecosystem, including patient management, patient cross referencing, User management, access controls, audit controls, provenance requirements, and eventually consent.
- This ecosystem will be constrained following the IHE profiles, but should be able to be standalone as well. That is that it is envisioned to be equally an API to an XDS ecosystem, or deployed as a standalone Document Sharing system purely FHIR based.
- This IG will leverage existing IHE profile of the current profiles that use FHIR (MHD, PIXm, PDQm, ATNAm, and MHD-I), use of IUA, and likely future Consent profile.
Profiled Resource(s)
- DocumentReference
- DocumentManifest
- List (as Document Folder)
- Patient
- Operation (as part of PIXm)
- AuditEvent
- ImagingObjectSelection
Constraints to be Applied
- minor constraints as found in the profiles
Extensions to be Applied
- None expected
Example Scenarios
As a FHIR centric Document Sharing Ecosystem
todo
As a proxy to an XDS or XCA Document Sharing Ecosystem
todo
Scope of coverage
Realm
Universal
Ownership
Owning committee name
Contributing or Reviewing Work Groups
- Struct Documents
- Imaging
- PA
- Security
Expected implementations
- much interest in IHE
- much interest in Argonaut
gForge Users
FHIR Profile Development Project Insight ID
tbd
Plans
Timelines
- 2016
Balloting Requirements
Choose one:
- Ballot with next FHIR DSTU or Normative Edition
- or Ballot independently as DSTU
- or Realm specific ballot
- or No Ballot
Desired Ballot Date
- 2016