We'd like to use the enrollmentrequest and response resources in our current implementation of R4. I see this is a stub and in the draft state. As an implementer what can we do to make this resource more generic, say for example, enrollment in a patient portal instead of restricting it to insurance only. It seemed to have been more generic in DSTU2. https://www.hl7.org/fhir/dstu2/enrollmentrequest.html 1
Here's our use case:
We're an oncology information system working with a number of patient portals. The patient, who is already registered in our HIS, is invited to join the portal- we send an enrollment request to the portal with all pertinent demographics including email of the patient. Portal invites the patient through the email provided. Patient enrolls in the portal through the portal invite email. We then asynchronously query the portal for all enrollment updates using a timestamp. This is the invite/register usecase. Once registered in the portal, other clinical info is exchanged using standard FHIR resources.
The enrollmentrequest/ response resources seem to fit very nicely into this workflow-
thanks to @Lloyd McKenzie for pointing me to these resources!