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

Difference between revisions of "201709 MHD STU3"

From HL7Wiki
Jump to navigation Jump to search
(MHD STU3 Document Exchange and Retrieval)
Line 8: Line 8:
  
 
==Justification==
 
==Justification==
<!--Test the use of document reference, document manifest and binary resources as defined by IHE MHD for STU 3 resources  - We are working in a project that could be the basis for several  regional/national EHR document exchanges, also to advance all the Document infrastructure to a higher FMM level. -->
+
Test the use of document reference, document manifest and binary resources as defined by IHE MHD for STU 3 resources  - We are working in a project that could be the basis for several  regional/national EHR document exchanges, also to advance all the Document infrastructure to a higher FMM level.  
  
 
==Proposed Track Lead==
 
==Proposed Track Lead==
<!-- Kaminker Diego, kaminker.diego@gmail.com, skypeid: diegokaminker -->
+
Kaminker Diego, kaminker.diego@gmail.com, skypeid: diegokaminker  
 
See [[Connectathon_Track_Lead_Responsibilities]]
 
See [[Connectathon_Track_Lead_Responsibilities]]
  
 
==Expected participants==
 
==Expected participants==
<!-- Fernando Campos , Hospital Italiano de Buenos Aires, AMBADOCList of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
+
Fernando Campos , Hospital Italiano de Buenos Aires, AMBADOC
 +
Diego Kaminker, Kern-IT SRL, AMBADOC
  
 
==Roles==
 
==Roles==
 
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
 
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
 
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
 
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
===Role 1 Name===
+
===Document Source===
<!-- Provide a description of the capabilities this role will have within the connectathon -->
+
Generates documents to be stored in a repository or referenced in a registry
 +
===Document Registry===
 +
Stores and provides a directory of existing and available documents
 +
===Document Repository===
 +
Stores and provides the actual content of the documents (binary)
 +
===Document Consumer===
 +
Search for documents in registries ( based on their metadata) and retrieves documents from repositories.
  
 
==Scenarios==
 
==Scenarios==

Revision as of 13:50, 31 May 2017


MHD STU3 Document Exchange and Retrieval

Submitting WG/Project/Implementer Group

Justification

Test the use of document reference, document manifest and binary resources as defined by IHE MHD for STU 3 resources - We are working in a project that could be the basis for several regional/national EHR document exchanges, also to advance all the Document infrastructure to a higher FMM level.

Proposed Track Lead

Kaminker Diego, kaminker.diego@gmail.com, skypeid: diegokaminker See Connectathon_Track_Lead_Responsibilities

Expected participants

Fernando Campos , Hospital Italiano de Buenos Aires, AMBADOC Diego Kaminker, Kern-IT SRL, AMBADOC

Roles

Please include information here regarding how much advance preparation will be required if creating a client and/or server.

Document Source

Generates documents to be stored in a repository or referenced in a registry

Document Registry

Stores and provides a directory of existing and available documents

Document Repository

Stores and provides the actual content of the documents (binary)

Document Consumer

Search for documents in registries ( based on their metadata) and retrieves documents from repositories.

Scenarios

Scenario Step 1 Name

Action:
Precondition:
Success Criteria:
Bonus point:


TestScript(s)