Acknowledgement Test scripts
2.0.0 - release

This page is part of the DK MedCom Acknowledgement TestScripts (v2.0.0: Release) based on FHIR R4. . For a full list of available versions, see the Directory of published versions

TestScript: Acknowledgement_TestScript_receive-fatal-error-duplicate

Official URL: http://medcomfhir.dk/ig/acknowledgementtestscript/acknowledgement-receive-fatal-error-duplicate Version: 2.0.0
Active as of 2023-05-25 Responsible: MedCom Computable Name: AcknowledgementTestScript

Copyright/Legal: MedCom 2023

Receive duplicate acknowledgement - Fatal Error

Generated Narrative: TestScript

Resource TestScript "acknowledgement-receive-fatal-error-duplicate"

Profile: AEGIS Touchstone Testing TestScript Profile

url: http://medcomfhir.dk/ig/acknowledgementtestscript/acknowledgement-receive-fatal-error-duplicate

version: 2.0.0

name: AcknowledgementTestScript

title: Receive duplicate acknowledgement - Fatal Error

status: active

date: 2023-05-25

publisher: MedCom

contact: MedCom: mailto:fhir@medcom.dk

description: Receive duplicate acknowledgement - Fatal Error

copyright: MedCom 2023

Origins

-IndexProfile
*1FHIR Client (Details: http://terminology.hl7.org/CodeSystem/testscript-profile-origin-types code FHIR-Client = 'FHIR Client', stated as 'null')

Destinations

-IndexProfile
*1FHIR Server (Details: http://terminology.hl7.org/CodeSystem/testscript-profile-destination-types code FHIR-Server = 'FHIR Server', stated as 'null')

fixture

id

create-fatal-error-01

autocreate: false

autodelete: false

resource: /FHIRSandbox/MedCom/Acknowledgement/draft/Receive/Fixtures/Acknowledgement-fixture-fatal-error.xml

fixture

id

create-fatal-error2-02

autocreate: false

autodelete: false

resource: /FHIRSandbox/MedCom/Acknowledgement/draft/Receive/Fixtures/Acknowledgement-fixture-fatal-error.xml

variable

name: destinationUri-fatal-error

expression: Bundle.entry.resource.ofType(MessageHeader).destination.endpoint

sourceId: create-fatal-error-01

variable

name: bundleid-fatal-error-01

expression: Bundle.id

sourceId: create-fatal-error-01

variable

name: messageHeaderid-fatal-error

expression: Bundle.entry[0].fullUrl

sourceId: create-fatal-error-01

variable

name: destinationUri-fatal-error2

expression: Bundle.entry.resource.ofType(MessageHeader).destination.endpoint

sourceId: create-fatal-error2-02

variable

name: bundleid-fatal-error2-02

expression: Bundle.id

sourceId: create-fatal-error2-02

variable

name: messageHeaderid-fatal-error2

expression: Bundle.entry[0].fullUrl

sourceId: create-fatal-error2-02

setup

action

Operations

-TypeResourceDescriptionAcceptEncodeRequestUrlParams
*Delete (Details: http://terminology.hl7.org/CodeSystem/testscript-operation-codes code delete = 'Delete', stated as 'null')BundleSystem-generated search and delete operations from conditional delete on Bundle MessageHeader.destination.endpointxmltrue?message.destination-uri=${destinationUri-fatal-error}

action

Operations

-TypeResourceDescriptionAcceptContentTypeEncodeRequestUrlSourceId
*Create (Details: http://terminology.hl7.org/CodeSystem/testscript-operation-codes code create = 'Create', stated as 'null')BundleCreate the Bundle resource in XML format on the destination server.xmlxmltruecreate-fatal-error-01

action

Operations

-TypeResourceDescriptionAcceptContentTypeEncodeRequestUrlParamsSourceId
*Create using Update (Details: http://terminology.hl7.org/CodeSystem/testscript-operation-codes code updateCreate = 'Create using Update', stated as 'null')BundleUpdate the Bundle.id in XML format on the destination server, so it corresponds to $bundleid-fatal-error-01.xmlxmltrue/${bundleid-fatal-error-01}create-fatal-error-01

action

Asserts

-DescriptionDirectionOperatorResponseCodeWarningOnly
*Confirm that the returned HTTP status is okay or created.responsein200,201false

action

Operations

-TypeResourceDescriptionAcceptContentTypeEncodeRequestUrlSourceId
*Create (Details: http://terminology.hl7.org/CodeSystem/testscript-operation-codes code create = 'Create', stated as 'null')BundleCreate the Bundle resource in XML format on the destination server.xmlxmltruecreate-fatal-error2-02

action

Operations

-TypeResourceDescriptionAcceptContentTypeEncodeRequestUrlParamsSourceId
*Create using Update (Details: http://terminology.hl7.org/CodeSystem/testscript-operation-codes code updateCreate = 'Create using Update', stated as 'null')BundleUpdate the Bundle.id in XML format on the destination server, so it corresponds to $bundleid-fatal-error2-02.xmlxmltrue/${bundleid-fatal-error2-02}create-fatal-error2-02

action

Asserts

-DescriptionDirectionOperatorResponseCodeWarningOnly
*Confirm that the returned HTTP status is okay or created.responsein200,201false

test

id

message-read-fatal-error-01

name: Get a fatal-error message 01

description: GET a message. The expected response is a 200(OK) with a payload of the message resource in XML format.

action

Operations

-TypeResourceDescriptionAcceptDestinationEncodeRequestUrlOriginParams
*Read (Details: http://terminology.hl7.org/CodeSystem/testscript-operation-codes code read = 'Read', stated as 'null')BundleReceive messagexml1true1/${bundleid-fatal-error-01}

action

Asserts

-DescriptionDirectionOperatorResponseCodeWarningOnly
*Confirm that the returned HTTP status is okay or created.responsein200,201false

test

id

message-read-fatal-error2-02

name: Get a fatal-error2 message 02

description: GET a message. The expected response is a 200(OK) with a payload of the message resource in XML format.

action

Operations

-TypeResourceDescriptionAcceptDestinationEncodeRequestUrlOriginParams
*Read (Details: http://terminology.hl7.org/CodeSystem/testscript-operation-codes code read = 'Read', stated as 'null')BundleReceive messagexml1true1/${bundleid-fatal-error2-02}

action

Asserts

-DescriptionDirectionOperatorResponseCodeWarningOnly
*Confirm that the returned HTTP status is okay or created.responsein200,201false