I do apologize if the following question was asked before. I have searched for the previous post and haven’t found the similar post.
The question is regarding the value of converting event based v2 messages (received by the interface engine) into FHIR resources and uses the FHIR resources to serve up API requests, e.g. patient demographics, encounters, outpatient appointments, referrals, etc. The V2 to FHIR conversion can be implemented as an asynchronous process and keep the resulting FHIR resources in an FHIR based persistent layer for fast retrieval via RESTful APIs.
If this sounds something worth to do, the next question is around how the resources are better stored in the persistent layer, as FHIR Message Resources, or should be stored as separate FHIR resources?
Advice and recommendations are welcome.
Many thanks in advance.