ChAuditEventPpq4Example
type: Bundle
node role: treeRoot
id:
  v: ChAuditEventPpq4Example
type:
  v: batch
entry:
  resource: AuditEvent
    id:
      v: ChAuditEventPpq3CreateExample
    meta:
      profile:
        v: http://fhir.ch/ig/ch-epr-fhir/StructureDefinition/ChAuditEventPpq3Create
        link: http://fhir.ch/ig/ch-epr-fhir/StructureDefinition/ChAuditEventPpq3Create
    text:
      status:
        v: generated
      div: Generated Narrative: AuditEvent ChAuditEventPpq3CreateExample Profile: CH Audit Event for [PPQ-3] Create privacy policy type: Audit Event ID rest: Restful Operation subtype: unknown PPQ-3: Mobile Privacy Policy Feed, FHIR Restful Interactions create: create 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: Destination Role ID who: Community A requestor: false Networks - Address Type * http://example.com URI agent type: Source Role ID who: My e-Health App requestor: false Networks - Address Type * 192.168.1.1 IP Address Sources - Site Observer * 2.16.756.1.2.3 My e-Health App entity what: Identifier: urn:oid:2.16.756.5.30.1.127.3.10.3/761337610411353650 type: Audit event entity type 1: Person role: AuditEventEntityRole 1: Patient 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:uuid:9a420810-9666-4eab-92ef-3145286de9eb type: Audit event entity type 2: System Object role: AuditEventEntityRole 4: Domain Resource entity what: Identifier: 00-0af7651916cd43dd8448eb211c80319c-b7ad6b…
    type:
      system:
        v: http://terminology.hl7.org/CodeSystem/audit-event-type
      code:
        v: rest
      display:
        v: Restful Operation
    subtype:
      system:
        v: urn:e-health-suisse:event-type-code
      code:
        v: PPQ-3
      display:
        v: Mobile Privacy Policy Feed
    subtype:
      system:
        v: http://hl7.org/fhir/restful-interaction
      code:
        v: create
      display:
        v: create
    recorded:
      v: 2024-10-28T09:43:56Z
    outcome:
      v: 0
    agent:
      alt id:
        v: 2000000090092
      name:
        v: Martina Musterarzt
      requestor:
        v: true
    agent:
      requestor:
        v: false
    agent:
      requestor:
        v: false
    source:
      site:
        v: 2.16.756.1.2.3
  request:
    method:
      v: POST
    url:
      v: http://example.com/AuditEvent
entry:
  resource: AuditEvent
    id:
      v: ChAuditEventPpq3UpdateExample
    meta:
      profile:
        v: http://fhir.ch/ig/ch-epr-fhir/StructureDefinition/ChAuditEventPpq3Update
        link: http://fhir.ch/ig/ch-epr-fhir/StructureDefinition/ChAuditEventPpq3Update
    text:
      status:
        v: generated
      div: Generated Narrative: AuditEvent ChAuditEventPpq3UpdateExample Profile: CH Audit Event for [PPQ-3] Update privacy policy type: Audit Event ID rest: Restful Operation subtype: unknown PPQ-3: Mobile Privacy Policy Feed, FHIR Restful Interactions update: update 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: Destination Role ID who: Community A requestor: false Networks - Address Type * http://example.com URI agent type: Source Role ID who: My e-Health App requestor: false Networks - Address Type * 192.168.1.1 IP Address Sources - Site Observer * 2.16.756.4.5.6 Community A entity what: Identifier: urn:oid:2.16.756.5.30.1.127.3.10.3/761337610411353650 type: Audit event entity type 1: Person role: AuditEventEntityRole 1: Patient 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:uuid:9a420810-9666-4eab-92ef-3145286de9eb type: Audit event entity type 2: System Object role: AuditEventEntityRole 4: Domain Resource entity what: Identifier: 00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169…
    type:
      system:
        v: http://terminology.hl7.org/CodeSystem/audit-event-type
      code:
        v: rest
      display:
        v: Restful Operation
    subtype:
      system:
        v: urn:e-health-suisse:event-type-code
      code:
        v: PPQ-3
      display:
        v: Mobile Privacy Policy Feed
    subtype:
      system:
        v: http://hl7.org/fhir/restful-interaction
      code:
        v: update
      display:
        v: update
    recorded:
      v: 2024-10-28T09:43:56Z
    outcome:
      v: 0
    agent:
      alt id:
        v: 2000000090092
      name:
        v: Martina Musterarzt
      requestor:
        v: true
    agent:
      requestor:
        v: false
    agent:
      requestor:
        v: false
    source:
      site:
        v: 2.16.756.4.5.6
  request:
    method:
      v: POST
    url:
      v: http://example.com/AuditEvent
entry:
  resource: AuditEvent
    id:
      v: ChAuditEventPpq3DeleteExample
    meta:
      profile:
        v: http://fhir.ch/ig/ch-epr-fhir/StructureDefinition/ChAuditEventPpq3Delete
        link: http://fhir.ch/ig/ch-epr-fhir/StructureDefinition/ChAuditEventPpq3Delete
    text:
      status:
        v: generated
      div: Generated Narrative: AuditEvent ChAuditEventPpq3DeleteExample Profile: CH Audit Event for [PPQ-3] Delete privacy policy type: Audit Event ID rest: Restful Operation subtype: unknown PPQ-3: Mobile Privacy Policy Feed, FHIR Restful Interactions delete: delete 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: Custodian who: Community A requestor: false Networks - Address Type * http://example.com URI agent type: Application who: My e-Health App requestor: false Networks - Address Type * 192.168.1.1 IP Address Sources - Site Observer * 2.16.756.1.2.3 My e-Health App entity what: Identifier: urn:oid:2.16.756.5.30.1.127.3.10.3/761337610411353650 type: Audit event entity type 1: Person role: AuditEventEntityRole 1: Patient 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:uuid:9a420810-9666-4eab-92ef-3145286de9eb type: Audit event entity type 2: System Object role: AuditEventEntityRole 4: Domain Resource entity what: Identifier: 00-0af7651916cd43dd8448eb211c80319c-b7ad6b7169203331-00…
    type:
      system:
        v: http://terminology.hl7.org/CodeSystem/audit-event-type
      code:
        v: rest
      display:
        v: Restful Operation
    subtype:
      system:
        v: urn:e-health-suisse:event-type-code
      code:
        v: PPQ-3
      display:
        v: Mobile Privacy Policy Feed
    subtype:
      system:
        v: http://hl7.org/fhir/restful-interaction
      code:
        v: delete
      display:
        v: delete
    recorded:
      v: 2024-10-28T09:43:56Z
    outcome:
      v: 0
    agent:
      alt id:
        v: 2000000090092
      name:
        v: Martina Musterarzt
      requestor:
        v: true
    agent:
      requestor:
        v: false
    agent:
      requestor:
        v: false
    source:
      site:
        v: 2.16.756.1.2.3
  request:
    method:
      v: POST
    url:
      v: http://example.com/AuditEvent

system:
  v: http://terminology.hl7.org/CodeSystem/v3-ParticipationType
code:
  v: RESP
display:
  v: responsible party

system:
  v: urn:oid:2.16.756.5.30.1.127.3.10.6
code:
  v: HCP

system:
  v: urn:oid:2.16.756.5.30.1.127.3.10.5
code:
  v: NORM
display:
  v: Normal Access

system:
  v: http://dicom.nema.org/resources/ontology/DCM
code:
  v: 110152
display:
  v: Destination Role ID

v: Community A

v: 5

system:
  v: http://dicom.nema.org/resources/ontology/DCM
code:
  v: 110153
display:
  v: Source Role ID

v: My e-Health App

v: 192.168.1.1

v: 2

v: My e-Health App

system:
  v: urn:oid:2.16.756.5.30.1.127.3.10.3
value:
  v: 761337610411353650

v: 1

v: Person

v: 1

v: Patient

system:
  v: urn:ietf:rfc:3986

v: 2

v: System Object

v: 4

v: Domain Resource

v: 4

v: Other

v: 26

v: Processing Element

system:
  v: http://terminology.hl7.org/CodeSystem/v3-ParticipationType
code:
  v: RESP
display:
  v: responsible party

system:
  v: urn:oid:2.16.756.5.30.1.127.3.10.6
code:
  v: HCP

system:
  v: urn:oid:2.16.756.5.30.1.127.3.10.5
code:
  v: NORM
display:
  v: Normal Access

system:
  v: http://dicom.nema.org/resources/ontology/DCM
code:
  v: 110152
display:
  v: Destination Role ID

v: Community A

v: 5

system:
  v: http://dicom.nema.org/resources/ontology/DCM
code:
  v: 110153
display:
  v: Source Role ID

v: My e-Health App

v: 192.168.1.1

v: 2

v: Community A

system:
  v: urn:oid:2.16.756.5.30.1.127.3.10.3
value:
  v: 761337610411353650

v: 1

v: Person

v: 1

v: Patient

system:
  v: urn:ietf:rfc:3986

v: 2

v: System Object

v: 4

v: Domain Resource

v: 4

v: Other

v: 26

v: Processing Element

system:
  v: http://terminology.hl7.org/CodeSystem/v3-ParticipationType
code:
  v: RESP
display:
  v: responsible party

system:
  v: urn:oid:2.16.756.5.30.1.127.3.10.6
code:
  v: HCP

system:
  v: urn:oid:2.16.756.5.30.1.127.3.10.5
code:
  v: NORM
display:
  v: Normal Access

system:
  v: http://terminology.hl7.org/CodeSystem/provenance-participant-type
code:
  v: custodian
display:
  v: Custodian

v: Community A

v: 5

system:
  v: http://dicom.nema.org/resources/ontology/DCM
code:
  v: 110150
display:
  v: Application

v: My e-Health App

v: 192.168.1.1

v: 2

v: My e-Health App

system:
  v: urn:oid:2.16.756.5.30.1.127.3.10.3
value:
  v: 761337610411353650

v: 1

v: Person

v: 1

v: Patient

system:
  v: urn:ietf:rfc:3986

v: 2

v: System Object

v: 4

v: Domain Resource

v: 4

v: Other

v: 26

v: Processing Element