This wiki has undergone a migration to Confluence found Here
Difference between revisions of "201808 Case Reporting"
Jump to navigation
Jump to search
(→Roles) |
|||
| Line 24: | Line 24: | ||
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 --> | ||
| − | === | + | ===Reporting Jurisdiction/Agency=== |
| − | + | ||
| + | |||
| + | ===Provider Organization=== | ||
==Scenarios== | ==Scenarios== | ||
Revision as of 13:43, 1 November 2017
Case Reporting
Submitting WG/Project/Implementer Group
PHER
Justification
Electronic case reporting has been maturing in the CDA product family, and FHIR case reporting specifications are now being being developed. This track will explore various aspects of FHIR case reporting as they mature, beginning with trigger code representation and dissemination, expanding to decision support logic and FHIR case reports as those aspects mature.
Proposed Track Lead
- John Loonsk
- Rick Geimer
See Connectathon_Track_Lead_Responsibilities
Expected participants
- TBD
Roles
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
Reporting Jurisdiction/Agency
Provider Organization
Scenarios
Scenario Step 1 Name
- Action:
- Precondition:
- Success Criteria:
- Bonus point:
