This wiki has undergone a migration to Confluence found Here
Difference between revisions of "201808 Case Reporting"
Jump to navigation
Jump to search
| Line 33: | Line 33: | ||
=== Update Trigger Codes === | === Update Trigger Codes === | ||
| − | :Action: | + | :Action: Reporting Jurisdiction/Agency determines that the current trigger code value sets require an update. The appropriate value sets are updated using PUT. |
| − | :Precondition: | + | :Precondition: Original trigger code value sets exist on test server |
| − | :Success Criteria: | + | :Success Criteria: Value sets are successfully updated and can be retrieved on demand with GET |
:Bonus point: <!-- Any additional complexity to make the scenario more challenging --> | :Bonus point: <!-- Any additional complexity to make the scenario more challenging --> | ||
Revision as of 14:15, 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
Update Trigger Codes
- Action: Reporting Jurisdiction/Agency determines that the current trigger code value sets require an update. The appropriate value sets are updated using PUT.
- Precondition: Original trigger code value sets exist on test server
- Success Criteria: Value sets are successfully updated and can be retrieved on demand with GET
- Bonus point:
