These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Public Health Surveillance
- Integrations and source ownership
Integrations and source ownership
Plan external notification, immunization and payment connections around source records.
- Public Health Surveillance
- Disease notification destination
- Immunization registry
- Payment service
Systems to connect
- Disease notification destination. If the program sends report data outside the app, agree which facility and condition identifiers the destination expects and who reconciles an accepted result.
- Immunization registry. If administered doses are sent externally, use the patient, provider, vaccine, lot and administration date from the dose record as the source for the handoff.
- Payment service. If payments arrive from a processor, reconcile its reference and received amount against the patient payment record.
How connections are governed
Assign an owner to each connection before use. That owner decides which data may leave the app, how errors are returned and how duplicate submissions are recognized. Keep the local report, vaccination or payment record linked to its original source. A message sent elsewhere does not by itself change the local review status. Rehearse one accepted result and one rejected result before including a connection in the operating cycle.
Set up Public Health Surveillance your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.