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

Difference between revisions of "DocumentSharing FHIR Profile Proposal"

From HL7Wiki
Jump to navigation Jump to search
(Created page with " {{subst::Template:FHIR Profile Proposal}}")
 
Line 14: Line 14:
  
  
=PutProposedProfileNameHere=
+
=DocumentSharing=
  
 
<!-- Profile names should meet the following characteristics:
 
<!-- Profile names should meet the following characteristics:
Line 30: Line 30:
  
 
==Profile balloting plans==
 
==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.
  
==Profile Details==
 
  
 
===Profiled Resource(s)===
 
===Profiled Resource(s)===
  
 
<!--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.-->
* [[ParentResourceAddress|ResourceName]]
+
* DocumentReference
 +
* DocumentManifest
 +
* List (as Document Folder)
 +
* Patient
 +
* Operation (as part of PIXm)
 +
* AuditEvent
 +
* ImagingObjectSelection
 +
 
  
 
====Constraints to be Applied====
 
====Constraints to be Applied====
  
 
<!--Describe how the current resource will be constrained.-->
 
<!--Describe how the current resource will be constrained.-->
* Constraint 1
+
* minor constraints as found in the profiles
* Constraint 2
+
 
  
 
====Extensions to be Applied====
 
====Extensions to be Applied====
  
 
<!--Describe how the current resource will be extended.-->
 
<!--Describe how the current resource will be extended.-->
* Extension 1
+
* None expected
* Extension 2
+
 
  
 
===Example Scenarios===
 
===Example Scenarios===
  
 
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this Profile.  They should demonstrate the full scope of the Profile and allow exercising of the Profiles capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) -->
 
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this Profile.  They should demonstrate the full scope of the Profile and allow exercising of the Profiles capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) -->
 +
====As a FHIR centric Document Sharing Ecosystem====
 +
todo
 +
====As a proxy to an XDS or XCA Document Sharing Ecosystem ====
 +
todo
  
 
===Scope of coverage===
 
===Scope of coverage===
Line 69: Line 86:
  
 
===Realm===
 
===Realm===
Please describe the realm to which this profile applies, or indicate that it is realm neutral.
+
Universal
  
 
==Ownership==
 
==Ownership==
Line 75: Line 92:
  
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the Profiles. -->
 
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the Profiles. -->
[[YourCommitteeName]]
+
[[HSI]]
  
 
===Contributing or Reviewing Work Groups===
 
===Contributing or Reviewing Work Groups===
  
 
<!-- 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) -->
* Work Group Name
+
* Struct Documents
* or link
+
* Imaging
* or "None"
+
* PA
 +
* Security
 +
 
  
 
===Expected implementations===
 
===Expected 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. -->
 
<!--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 Argonaut
  
 
===gForge Users===
 
===gForge Users===
Line 96: Line 117:
  
 
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
 
<!-- Please specify the id of your work group’s PSS for doing FHIR work.  (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc -->
 +
tbd
  
 
==Plans==
 
==Plans==
Line 101: Line 123:
  
 
<!-- Indicate the target date for having the Profile complete from a committee perspective and ready for vetting and voting -->
 
<!-- Indicate the target date for having the Profile complete from a committee perspective and ready for vetting and voting -->
*TargetDateForInternalReview
+
*2016
  
 
===Balloting Requirements===
 
===Balloting Requirements===
Line 115: Line 137:
 
<!-- Indicate the desired ballot date.-->
 
<!-- Indicate the desired ballot date.-->
 
Desired Ballot Date
 
Desired Ballot Date
*PutDesiredBallotDateHere
+
*2016

Revision as of 20:51, 14 January 2016



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

HSI

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