Difference between revisions of "201709 MHD STU3"
(MHD STU3 Document Exchange and Retrieval) |
JohnMoehrke (talk | contribs) |
||
| (10 intermediate revisions by 2 users not shown) | |||
| Line 5: | Line 5: | ||
==Submitting WG/Project/Implementer Group== | ==Submitting WG/Project/Implementer Group== | ||
| − | + | ALMADOC Buenos Aires, Argentina | |
==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. | |
==Proposed Track Lead== | ==Proposed Track Lead== | ||
| − | + | Kaminker Diego, kaminker.diego@gmail.com, skypeid: diegokaminker | |
| + | |||
| + | John Moehrke, JohnMoehrke@gmail.com, skypeid: johnmoehrke | ||
| + | |||
See [[Connectathon_Track_Lead_Responsibilities]] | See [[Connectathon_Track_Lead_Responsibilities]] | ||
==Expected participants== | ==Expected participants== | ||
| − | + | Fernando Campos , Hospital Italiano de Buenos Aires, ALMADOC | |
| + | Diego Kaminker, Kern-IT SRL, ALMADOC | ||
==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 --> | ||
| − | === | + | ===Document Source=== |
| − | + | Generates documents to be stored in a repository or referenced in a registry. | |
| + | Documents can be in PDF,TXT, image (PNG, JPG) or XML (i.e. CDA R2 ) format | ||
| + | |||
| + | ===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== | ||
| − | + | :1.New Document Created by Document Source (1 binary attachment) | |
| + | :2.New Document Created by Document Source (no binary attachment -ref) | ||
| + | :3.New Document Created by Document Source (>1 binary attachment) | ||
| + | :4.Document Consumer Search by Filter Combination (subject, class, type, date range) | ||
| + | :5.Direct Binary Document Retrieval by Document Consumer | ||
===Scenario Step 1 Name=== | ===Scenario Step 1 Name=== | ||
| Line 38: | Line 54: | ||
These should be committed to SVN under trunk/connectathons/[connectathon] | These should be committed to SVN under trunk/connectathons/[connectathon] | ||
--> | --> | ||
| + | |||
| + | ==Report out from Connectathon == | ||
| + | https://www.dropbox.com/s/hrbuj69fs1x61er/MHD_STU3_TRACK.pptx?dl=0 | ||
| + | |||
| + | |||
| + | Blog post reportout https://healthcaresecprivacy.blogspot.com/2017/09/fhir-connectathon-of-ihe-mhd-profile.html | ||
Latest revision as of 18:54, 11 September 2017
MHD STU3 Document Exchange and Retrieval
Submitting WG/Project/Implementer Group
ALMADOC Buenos Aires, Argentina
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
John Moehrke, JohnMoehrke@gmail.com, skypeid: johnmoehrke
See Connectathon_Track_Lead_Responsibilities
Expected participants
Fernando Campos , Hospital Italiano de Buenos Aires, ALMADOC Diego Kaminker, Kern-IT SRL, ALMADOC
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. Documents can be in PDF,TXT, image (PNG, JPG) or XML (i.e. CDA R2 ) format
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
- 1.New Document Created by Document Source (1 binary attachment)
- 2.New Document Created by Document Source (no binary attachment -ref)
- 3.New Document Created by Document Source (>1 binary attachment)
- 4.Document Consumer Search by Filter Combination (subject, class, type, date range)
- 5.Direct Binary Document Retrieval by Document Consumer
Scenario Step 1 Name
- Action:
- Precondition:
- Success Criteria:
- Bonus point:
TestScript(s)
Report out from Connectathon
https://www.dropbox.com/s/hrbuj69fs1x61er/MHD_STU3_TRACK.pptx?dl=0
Blog post reportout https://healthcaresecprivacy.blogspot.com/2017/09/fhir-connectathon-of-ihe-mhd-profile.html
