OpenSRP atomfeed module is based on ICT4H Atomfeed Module . This module creates feeds for different transactions happening into OpenMRS.
Rightnow feeds are available for Patient data Save and Update and Encounter data Save and Update. Full implementation would have following
Entity Type | Child Entity | Transaction Type | Is Available | API Method | Category |
---|---|---|---|---|---|
Patient | Patient Demographics | Save, Update, Void | Yes | savePatient | OpenSRP_Patient |
Patient Identifier | Save, Update, Void | Yes | savePatient | OpenSRP_Patient | |
Patient Address | Save, Update, Void | Yes | savePatient | OpenSRP_Patient | |
Patient Attributes | Save, Update, Void | Yes | savePatient | OpenSRP_Patient | |
Encounter | Encounter Data | Save, Update, Void | Yes | saveEncounter | OpenSRP_Encounter |
Observations | Save, Update, Void | Yes | saveEncounter | OpenSRP_Encounter | |
Order | Drug Orders | save, Update, Void | Yes | saveOrder | OpenSRP_DrugOrder |
Cohort | Cohort Data | Save, Update, Void | No | saveCohort | OpenSRP_Cohort |
Cohort Attributes | Save, Update, Void | No | saveCohort | OpenSRP_Cohort | |
Cohort Members | Save, Update, Void | No | saveCohort | OpenSRP_Cohort | |
Relationship | Patient Relationship | Save, Update, Void | No | saveRelationship, voidRelationship, purgeRelationship | OpenSRP_Relationship |
Note: The highlighted part shows new addition to original module. This module is supposed to work well with orignal module without any conflicts and is using same tables to maintain feeds. The category used by this module has Prefix OpenSRP_category-type. Hence system interested in OpenSRP feeds should be able to distinguish feeds generated by both systems.