EDS Test Scripts
0.1.0 - ci-build Denmark flag

EDS Test Scripts, published by MedCom. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/medcomdk/dk-ehmi-eds-testscripts/ and changes regularly. See the Directory of published versions

TestScript: Test for ANS.2 - Message Type Searching

Official URL: http://medcomehmi.dk/ig/edstestscripts/ANS2TestMessageTypeSearch Version: 0.1.0
Active as of 2025-08-18 Computable Name: ANS2TestMessageTypeSearch

Copyright/Legal: MedCom 2025

Profile: http://touchstone.aegis.net/touchstone/fhir/testing/StructureDefinition/testscript

url: TestScript ANS2TestMessageTypeSearch

version: 0.1.0

name: ANS2TestMessageTypeSearch

status: Aktiv

date: 2025-08-18

publisher: MedCom

contact: MedCom: https://medcom.dk,ehmi@medcom.dk

jurisdiction: Denmark

copyright:

MedCom 2025

Origins

-IndexProfile
*1Test script profile origin type FHIR-Client: FHIR Client

Destinations

-IndexProfile
*1Test script profile destination type FHIR-Server: FHIR Server

fixture

id

C1EUAEDSPatientDeliveryStatus

autocreate: false

autodelete: false

resource: ./Fixtures/AuditEvent-C1EUAToEdsFixture.json

profile: http://medcomehmi.dk/ig/eds/StructureDefinition/EdsPatientDeliveryStatus

variable

name: IdOfResourceToBeCreated

expression: id

sourceId: C1EUAEDSPatientDeliveryStatus

variable

name: MessageTypeOfCreatedResource

expression: entity.detail.where(type = 'ehmiMessageType').value

sourceId: C1EUAEDSPatientDeliveryStatus

setup

action

Operations

-TypeResourceDescriptionDestinationEncodeRequestUrlOriginParams
*Test script operation code delete: DeleteAuditEventDeletes the resource we intend to create later, to ensure it doesn't already exist on the server from previously run tests1true1/${IdOfResourceToBeCreated}

test

id

CreatePatientDeliveryStatus

name: ANS2 Create

description: Use case ANS2 create PatientDeliveryStatus object on the SUT in order to search for it later

action

Operations

-TypeResourceDescriptionDestinationEncodeRequestUrlOriginParamsSourceId
*Test script operation code update: UpdateAuditEventCreate a PatientDeliveryStatus AuditEvent resource on the SUT1true1/${IdOfResourceToBeCreated}C1EUAEDSPatientDeliveryStatus

action

Asserts

-DescriptionDirectionResponseWarningOnly
*Ensure the PatientDeliveryStatus AuditEvent was createdresponsecreatedfalse

test

id

SearchPatientDeliveryStatusWithMessageType

name: ANS2 search

description: Use case ANS2 search for the created PatientDeliveryStatus object on the SUT with ehmiMessageType

action

Operations

-TypeResourceDescriptionDestinationEncodeRequestUrlOriginParams
*Test script operation code search: SearchAuditEventSearch for the PatientDeliveryStatus AuditEvent with the type being ${MessageTypeOfCreatedResource}1true1?ehmiMessageType=${MessageTypeOfCreatedResource}

action

Asserts

-DescriptionDirectionExpressionOperatorValueWarningOnly
*Ensure the PatientDeliveryStatus AuditEvent is foundresponseBundle.entry.where(resource.resourceType = 'AuditEvent' and resource.id = '${IdOfResourceToBeCreated}').count()equals1false

test

id

SearchPatientDeliveryStatusInvalidMessageType

name: ANS2 invalid search

description: Use case ANS2 search for the created PatientDeliveryStatus object on the SUT with an invalid message type. Not expecting to find it

action

Operations

-TypeResourceDescriptionDestinationEncodeRequestUrlOriginParams
*Test script operation code search: SearchAuditEventSearch for the PatientDeliveryStatus AuditEvent with an invalid message type1true1?ehmiMessageType=invalid

action

Asserts

-DescriptionDirectionExpressionOperatorValueWarningOnly
*Ensure the PatientDeliveryStatus AuditEvent is not found with an invalid message typeresponseBundle.entry.where(resource.resourceType = 'AuditEvent' and resource.id = '${IdOfResourceToBeCreated}').count()equals0false