Stream: implementers
Topic: Monitoring HL7v2 and FHIR Servers
Kevin Mayfield (Nov 20 2016 at 10:10):
I'm looking at exposing events/metrics to our performance monitoring system (splunk). The data I'm looking at monitoring would be HL7v2 events such as Patient Create/Update, Encounter plus class (inpatient, outpatient, etc), Integration Engine Info/warn/error logs (as OperationOutcome) and custom metrics. It would seem AuditEvent is what I should be basing this on, which alongside the normal resource will contain an abstract version of the original resource. These AuditEvents would be posted to splunk.
Kevin Mayfield (Nov 20 2016 at 10:13):
Does this make sense and/or has anyone done anything similar? [We would only be doing a limited conversion to FHIR for HL7v2 messages and the conversion is desirable to expose HL7v2 developers to FHIR+REST]
Grahame Grieve (Nov 20 2016 at 10:15):
The nearest similar thing I know of was when @Simone Heckmann set up to post an AuditEvent for fhir2.healthintersections.com.au for any tweet with #FHIR in it
Grahame Grieve (Nov 20 2016 at 10:15):
it makes sense to use AuditEvent
Simone Heckmann (Nov 21 2016 at 19:13):
IIRC I used Communication Resource for the Twitter spoof, I don't remember doing anything with AuditEvent. In combination with V2 Mapping I only tackled Provenance but not AuditEvent yet. I understood this to be rather something the server would want to create when it recieves e.g. a Transaction, rather than the client, when it posts one...
Grahame Grieve (Nov 21 2016 at 19:53):
client could post an AuditEvent (ATNA server)
Kevin Mayfield (Nov 22 2016 at 12:31):
@Simone Heckmann Yes, that's what I was thinking of. When a transaction comes in, the v2 message would carry on as normal but we'd additionally audit the transaction using FHIR. A background process would send the audit to splunk for telemetry.
Last updated: Apr 12 2022 at 19:14 UTC
