Generated Narrative: AuditEvent ChAuditEventIti90ReadExample Profile: CH Audit Event for [ITI-90] Query Client & Directory / Read type: Audit Event ID rest: RESTful Operation subtype: unknown ITI-90: Find Matching Care Services, FHIR Restful Interactions read: read recorded: 2024-10-28 09:43:56+0000 outcome: Success agent type: responsible party role: Healthcare professional altId: 2000000090092 name: Martina Musterarzt requestor: true purposeOfUse: Normal Access agent type: Source Role ID who: My e-Health App requestor: false Networks - Address Type * 192.168.1.1 IP Address agent type: Destination Role ID who: Community A requestor: false Networks - Address Type * https://example.com URI Sources - Site Observer * 2.16.756.1.2.3 My e-Health App entity what: Identifier: 00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-00 type: Audit event entity type 4: Other role: AuditEventEntityRole 26: Processing Element entity what: Identifier: <a href="http://terminology.hl7.org/6.2.0/NamingSystem-uri.html" title="As defined by RFC 3986 (http://www.ietf.org/rfc/rfc3986.txt)(with many schemes defined in many RFCs). For OIDs and UUIDs, use the URN form (urn:oid:(note: lowercase) and urn:uuid:). See http://www.ietf.org/rfc/rfc3001.txt and http://www.ietf.org/rfc/rfc4122.txt This oid is used as an identifier II.root to indicate the the extension is an absolute URI (technically, an IRI). Typically, this is used for OIDs and GUIDs. Note that when this OID is used with OIDs and GUIDs, the II.extension should start with urn:oid or urn:uuid: Note that this OID is created to aid with interconversion between CDA and FHIR - FHIR uses urn:ietf:rfc:3986 as equivalent to this OID. URIs as identifiers appear more commonly in FHIR. This OID may also be used in CD.codeSystem.">Uniform Resource Identifier (URI)/urn:oid:2.16.10.89.203 type: Audit event entity type 2: System Object role: AuditEventEntityRole 4: Domain Resource