201808 Case Reporting

Electronic 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 in future Connectathons.

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

Jurisdiction or agency that will receive case reports, and that is responsible for managing and disseminating trigger codes.

Provider Organization

Organization that submits case reports based on trigger codes, and receives trigger code updates.

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. Also update trigger codes as a Bundle of ValueSet resources as a whole.

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:

Subscribe to Trigger Code Updates

Action: Provider organization uses Subscription to subscribe to changes to trigger code value sets (or value set Bundle) using any legal notification method.

Precondition: Original trigger code value sets exist on test server

Success Criteria: Provider organization is notified and receives a copy of any trigger code value sets that are updated

Bonus point: