Question 1 of 3
How does SyncApp handle data fetched from a PMS with an inconsistent format before sending it to the Data Service?
AIt sends the raw data and lets Data Service handle normalization
BIt rejects data that doesn't match the Weave schema
CIt transforms (serializes) the data into a predefined Weave entity schema before sending
DIt stores the raw data in a local database and transforms it on request
Question 2 of 3
For an on-prem PMS, where does the SyncApp process run?
AOn a Kubernetes pod in Weave's cloud infrastructure
BOn a shared server at Weave's data center
COn the customer's/client's own machine, co-located with the PMS database
DOn a cloud VM provisioned specifically for that customer
Question 3 of 3
Why does SyncApp store the hash of transformed data?
ATo encrypt sensitive patient data before sending to Data Service
BTo verify that the Data Service received the data correctly
CTo detect whether data has actually changed and avoid sending unchanged records to Data Service
DTo create audit logs for HIPAA compliance