-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Proposed Subscription Design Change
In the fall of 2018, we have been modifying the HAPI-FHIR Server to improve support for running the subscription matching functionality in a separate process from the REST server functionality. This has happened in stages:
In-memory matcher added a new class SubscriptionMatcherInMemory that matches incoming resources against subscription criteria by examining the content within the resource directly as opposed to querying the database.
Standalone subscription added a new maven module called hapi-fhir-jpaserver-subscription and moved classes there from hapi-fhir-jpaserver-base so that the SubscriptionMatcherInMemory had everything it needed to match resources against subscription criteria without access to a database. Shared classes needed by both hapi-fhir-jpaserver-subscription and hapi-fhir-jpaserver-base were moved into two new maven modules called hapi-fhir-jpaserver-model and hapi-fhir-jpaserver-searchparam.