Hello @pranavfj, currently, there is no endpoint in OpenMRS for returning the IPS (See available profiles here). The setup being referred to by @dkayiwa would be achieved by using FHIR data pipes to stream your OpenMRS resources into a HAPI FHIR server that has built-in functionality to return an IPS. Here is a sample set up.
There isn’t currently built-in support for the IPS $summary operation in OpenMRS, though we did build an IPS ingestion and viewing tool (what @dkayiwa referenced).
The architecture @reagan suggests is something we’ve suggested using because often when constructing a “real-world“ IPS, you would want to merge resources from multiple systems.
While the $summary operation itself is not implemented, most of the resources for an IPS (MedicationStatement is the big missing thing) are and our profiles are (given appropriate configuration of the client side) generally compatible with the IPS profiles (though some finessing via Mirth maybe needed). There is, therefore, also the option of extracting the data via the FHIR API and transforming it into the IPS composition via an integration engine like MirthConnect.
We do have limited support for the standard $everything operation which creates a bundle of most of the data associated with the patient which could be processed into an IPS (though note that the $everything operation probably doesn’t perform particularly well). (By limited support I mean that we don’t process any of the “in parameters“ and it won’t return EpisodesOfCare of Groups associated with a patient, but should return everything else).