This wiki has undergone a migration to Confluence found Here
Difference between revisions of "201609 Attachments"
Jump to navigation
Jump to search
(→Roles) |
|||
| Line 27: | Line 27: | ||
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 --> | ||
| − | === | + | ===Payer=== |
| + | <!-- Provide a description of the capabilities this role will have within the connectathon --> | ||
| + | |||
| + | ===Provider=== | ||
<!-- Provide a description of the capabilities this role will have within the connectathon --> | <!-- Provide a description of the capabilities this role will have within the connectathon --> | ||
Revision as of 16:50, 17 June 2016
Attachments
Submitting WG/Project/Implementer Group
Attachments Work Group (AWG)
Justification
Proposed Track Lead
See Connectathon_Track_Lead_Responsibilities
- Rick Geimer
- Co-leads, Paul Knapp, Durwin Day
Expected participants
- BCBS
- HCSC
- BCBSAL
- Anthem
- Optum
Roles
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
Payer
Provider
Scenarios
Scenario Step 1 Name
- Action:
- Precondition:
- Success Criteria:
- Bonus point:
