HospitalNotification Testscripts
3.0.1 - ci-build

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

TestScript: HospitalNotification_TestScript_PF-receive-tec-05

Official URL: http://medcomfhir.dk/ig/hospitalnotificationtestscript/hospitalnotification-PF-receive-tec-05 Version: 3.0.1
Active as of 2023-05-25 Responsible: MedCom Computable Name: HospitalNotificationTestScript

Copyright/Legal: MedCom 2021

Receive: Receive a message on the 29th of February 2024 (leap year): Patient is admitted on the date of leap year

Generated Narrative: TestScript

Resource TestScript "hospitalnotification-PF-receive-tec-05"

Profile: AEGIS Touchstone Testing TestScript Profile

url: http://medcomfhir.dk/ig/hospitalnotificationtestscript/hospitalnotification-PF-receive-tec-05

version: 3.0.1

name: HospitalNotificationTestScript

title: Receive: Receive a message on the 29th of February 2024 (leap year): Patient is admitted on the date of leap year - PF-receive-tec-05

status: active

date: 2023-05-25

publisher: MedCom

contact: MedCom: mailto:fhir@medcom.dk

description: Receive: Receive a message on the 29th of February 2024 (leap year): Patient is admitted on the date of leap year

copyright: MedCom 2021

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-STIN-01

autocreate: false

autodelete: false

resource: /FHIRSandbox/MedCom/HospitalNotification/v300/Receive/Fixtures/HospitalNotification-fixture-STIN-leapyear.xml

profile: http://medcomfhir.dk/ig/hospitalnotification/StructureDefinition/medcom-hospitalNotification-message "MedComHospitalNotificationMessage"

variable

name: destinationUri-STIN

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

sourceId: create-STIN-01

variable

name: bundleid-STIN

expression: Bundle.id

sourceId: create-STIN-01

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-STIN}

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-STIN-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-STIN.xmlxmltrue/${bundleid-STIN}create-STIN-01

action

Asserts

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

test

id

hospitalnotification-read-STIN-01

name: Get a HospitalNotification STIN Message 01

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

action

Operations

-TypeResourceDescriptionAcceptContentTypeDestinationEncodeRequestUrlOriginParams
*Read (Details: http://terminology.hl7.org/CodeSystem/testscript-operation-codes code read = 'Read', stated as 'null')BundleReceive Hospital Notificationxmlxml1true1/${bundleid-STIN}

action

Asserts

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