Smart move.
That being said, at it’s heart the patientsummary module is simply a
wrapper around reporting Datasets and Renderers 
The patientsummary module creates the following wrapper objects:
- PatientSummaryReportDefinition (just a custom Report Definition that is fixed to contain a single Patient Data Set Definition)
- PatientSummaryTemplate (just a wrapper around a Report Design)
It then adds some service methods and UI pages (in the 1.x UI) to allow for more easily managing / editing these. And it attaches to 1.x UI extension points for allowing patient summaries to appear as new tabs on the patient dashboard based on global property configuration.
It is all described a bit better here: https://wiki.openmrs.org/display/docs/Patient+Summary+Module
So, if you are working in the 2.x UI, and can independently find a way to add a page that runs a Report containing a single PatientDataSetDefinition and renders it using a TextTemplateRenderer and outputs the resulting html to the page, then you’ve pretty much achieved what the patientsummary module is capable of doing.
Mike