CareCommunication Test scripts
5.0.0 - release Denmark flag

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

Artifacts Summary

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

1st message - Bruno Test Elmer

1st message - Patient described with minimal information. Valid only if used in a Bundle.

1st message - Bruno Test Elmer

1st message - Patient described with minimal information. Valid only if used in a Bundle.

1st message - Example of a reciever organization with a SOR and an EAN identifier.

1st message - Example of an organization with a SOR and an EAN identifier.

1st message - Example of a reciever organization with a SOR and an EAN identifier.

1st message - Example of an organization with a SOR and an EAN identifier.

1st message - Example of a sender organization with a SOR and an EAN identifier.

1st message - Example of an organization with a SOR and an EAN identifier.

1st message - Example of a sender organization with a SOR and an EAN identifier.

1st message - Example of an organization with a SOR and an EAN identifier.

Forward CareCommunication

Forward CareCommunication

Forward CareCommunication where the new message includes 1 attached file.

Forward CareCommunication where the new message includes 1 attached file.

Forward CareCommunication with 1 attachment and add 2 new attachments.

Forward CareCommunication with 1 attachment and add 2 new attachments.

Forward CareCommunication with changed category

Forward CareCommunication with changed category

Forward CareCommunication with changed topic

Forward CareCommunication with changed topic

Forward a part of the CareCommunication thread. Only the message text is expected to be forwarded

Forward a part of the CareCommunication thread. Only the message text is expected to be forwarded

MedCom Core Encounter

Example of a simple MedCom Core Encounter

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

PractitionerRole with a role and reference to a practitioner

Receive_Tek-A

Receive_Tek-A

Receive_Tek-A - Communication

Receive_Tek-A - Communication

Receive_Tek-A - MessageHeader

Receive_Tek-A - MessageHeader

Receive_Tek-A - Patient

Receive_Tek-A - Patient

Receive_Tek-A - Provenance

Receive_Tek-A - Provenance

Receive_Tek-A - Receiver

Receive_Tek-A - Receiver

Receive_Tek-A - Sender

Receive_Tek-A - Sender

Receive_Tek-A - practitioner

Receive_Tek-A - practitioner

Receive_Tek-A - practitionerRole

Receive_Tek-A - practitionerRole

Receive_Tek-B

Receive_Tek-B

Receive_Tek-B - Communication

Receive_Tek-B - Communication

Receive_Tek-B - MessageHeader

Receive_Tek-B - MessageHeader

Receive_Tek-B - Patient

Receive_Tek-B - Patient

Receive_Tek-B - Provenance

Receive_Tek-B - Provenance

Receive_Tek-B - Receiver

Receive_Tek-B - Receiver

Receive_Tek-B - Sender

Receive_Tek-B - Sender

Receive_Tek-B - practitioner

Receive_Tek-B - practitioner

Receive_Tek-B - practitionerRole

Receive_Tek-B - practitionerRole

Receive_Tek-C

Receive_Tek-C

Receive_Tek-C - Communication

Receive_Tek-C - Communication

Receive_Tek-C - MessageHeader

Receive_Tek-C - MessageHeader

Receive_Tek-C - Patient

Receive_Tek-C - Patient

Receive_Tek-C - Provenance

Receive_Tek-C - Provenance

Receive_Tek-C - Receiver

Receive_Tek-C - Receiver

Receive_Tek-C - Sender

Receive_Tek-C - Sender

Receive_Tek-C - practitioner

Receive_Tek-C - practitioner

Receive_Tek-C - practitionerRole

Receive_Tek-C - practitionerRole

Receive_Tek-D

Receive_Tek-D

Receive_Tek-D - Communication

Receive_Tek-D - Communication

Receive_Tek-D - MessageHeader

Receive_Tek-D - MessageHeader

Receive_Tek-D - Patient

Receive_Tek-D - Patient

Receive_Tek-D - Provenance

Receive_Tek-D - Provenance

Receive_Tek-D - Receiver

Receive_Tek-D - Receiver

Receive_Tek-D - Sender

Receive_Tek-D - Sender

Receive_Tek-D - practitioner

Receive_Tek-D - practitioner

Receive_Tek-D - practitionerRole

Receive_Tek-D - practitionerRole

Receive_Tek-E-new-parallel - Bruno Test Elmer

Receive_Tek-E-new-parallel - Patient described with minimal information. Valid only if used in a Bundle.

Receive_Tek-E-new-parallel - Example of a reciever organization with a SOR and an EAN identifier.

Receive_Tek-E-new-parallel - Example of an organization with a SOR and an EAN identifier.

Receive_Tek-E-new-parallel - Example of a sender organization with a SOR and an EAN identifier.

Receive_Tek-E-new-parallel - Example of an organization with a SOR and an EAN identifier.

Receive_Tek-E-new-parallel - Instance of Communication resource used in a new message.

Receive_Tek-E-new-parallel - Content of care communication message. Valid only if used in a bundle (message) - new message

Receive_Tek-E-new-parallel - Instance of a MessageHeader resource used in a new message.

Receive_Tek-E-new-parallel - Example of a MessageHeader in a new CareCommunication message. Valid only if used in a bundle (message).

Receive_Tek-E-new-parallel - New CareCommunication message.

Receive_Tek-E-new-parallel - Example of a CareCommunication new message.

Receive_Tek-F-reply-parallel - Instance of Communication resource used in a reply message.

Receive_Tek-F-reply-parallel - Content of care communication message. Valid only if used in a bundle (message) - reply message

Receive_Tek-F-reply-parallel - Instance of a MessageHeader resource used in a reply message.

Receive_Tek-F-reply-parallel - Example of a MessageHeader in a reply CareCommunication message. Valid only if used in a bundle (message).

Receive_Tek-F-reply-parallel - Reply CareCommunication message

Receive_Tek-F-reply-parallel - Example of a reply to a CareCommunication message.

Reply CareCommunication

Reply CareCommunication

Reply CareCommunication add two new attachments

Reply CareCommunication add two new attachments.

Reply CareCommunication to a CareCommunication send by the replying system

Reply CareCommunication to a CareCommunication send by the replying system

Reply CareCommunication to a CareCommunication that has been forwarded

Reply CareCommunication to a CareCommunication that has been forwarded

Reply CareCommunication where the new message includes one attached files

Reply CareCommunication where the new message includes one attached files.

Reply CareCommunication with changed category

Reply CareCommunication with changed category

Reply CareCommunication with changed topic

Reply CareCommunication with changed topic

Reply to CareCommunication, that includes all content, with a message segment only.

Reply to CareCommunication, that includes all content, with a message segment only.

Reply to CareCommunication, where episodeOfCare-identifier is correctly transfered in the communication

Reply to CareCommunication, where episodeOfCare-identifier is correctly transfered in the communication

S-D-new

S-D-new

S-D-new - Communication

S-D-new - Communication

S-D-new - MessageHeader

S-D-new - MessageHeader

S-D-new - Patient

S-D-new - Patient

S-D-new - Provenance

S-D-new - Provenance

S-D-new - Receiver

S-D-new - Receiver

S-D-new - Sender

S-D-new - Sender

S-D-new - practitioner

S-D-new - practitioner

S-D-new - practitionerRole

S-D-new - practitionerRole

Send CareCommunication where the patient has a CPR-number as identifier

Send CareCommunication where the patient has a CPR-number as identifier

Send CareCommunication where the patient has a replacement-CPR-number as identifier

Send CareCommunication where the patient has a replacement-CPR-number as identifier

Send CareCommunication with a bmp as an attached file.

Send CareCommunication with a bmp as an attached file.

Send CareCommunication with a episodeOfCare-identifier

Send CareCommunication with a episodeOfCare-identifier

Send CareCommunication with a gif as an attached file.

Send CareCommunication with a gif as an attached file.

Send CareCommunication with a jpeg as an attached file.

Send CareCommunication with a jpeg as an attached file.

Send CareCommunication with a link as an attachment.

Send CareCommunication with a link as an attachment.

Send CareCommunication with a multiple attached files.

Send CareCommunication with a multiple attached files.

Send CareCommunication with a pdf-document as an attached file.

Send CareCommunication with a pdf-document as an attached file.

Send CareCommunication with a png as an attached file.

Send CareCommunication with a png as an attached file.

Send CareCommunication with a tiff as an attached file.

Send CareCommunication with a tiff as an attached file.

Send CareCommunication with an attachment and structured author information.

Send CareCommunication with an attachment and structured author information.

Send CareCommunication with category 'Other'.

Send CareCommunication with category 'Other'.

Send CareCommunication with category 'Regarding referral', included priority.

Send CareCommunication with category 'Regarding referral', included priority.

Send CareCommunication with sender and recipient

Send CareCommunication with sender and recipient

Send CareCommunication with topic.

Send CareCommunication with topic.

Send CareCommunication.

Send CareCommunication.

Send-A-new

Send-A-new

Send-A-new - Communication

Send-A-new - Communication

Send-A-new - MessageHeader

Send-A-new - MessageHeader

Send-A-new - Patient

Send-A-new - Patient

Send-A-new - Provenance

Send-A-new - Provenance

Send-A-new - Receiver

Send-A-new - Receiver

Send-A-new - Sender

Send-A-new - Sender

Send-A-new - Sender Careteam

Send-A-new - Sender Careteam

Send-A-new - practitioner

Send-A-new - practitioner

Send-A-new - practitionerRole

Send-A-new - practitionerRole

Send-A-new - specifik Receiver practitioner

Send-A-new - specifik Receiver practitioner

Send-A-new - specifik Receiver practitionerRole

Send-A-new - specifik Receiver practitionerRole

Send-B-new

Send-B-new

Send-B-new - Communication

Send-B-new - Communication

Send-B-new - MessageHeader

Send-B-new - MessageHeader

Send-B-new - Patient

Send-B-new - Patient

Send-B-new - Provenance

Send-B-new - Provenance

Send-B-new - Receiver

Send-B-new - Receiver

Send-B-new - Sender

Send-B-new - Sender

Send-B-new - practitioner

Send-B-new - practitioner

Send-B-new - practitionerRole

Send-B-new - practitionerRole

Send-C-new

Send-C-new

Send-C-new - Communication

Send-C-new - Communication

Send-C-new - MessageHeader

Send-C-new - MessageHeader

Send-C-new - Patient

Send-C-new - Patient

Send-C-new - Provenance

Send-C-new - Provenance

Send-C-new - Receiver

Send-C-new - Receiver

Send-C-new - Sender

Send-C-new - Sender

Send-C-new - practitioner

Send-C-new - practitioner

Send-C-new - practitionerRole

Send-C-new - practitionerRole

Send-E-forward

Send-E-forward

Send-E-forward - Communication

Send-E-forward - Communication

Send-E-forward - MessageHeader

Send-E-forward - MessageHeader

Send-E-forward - MessageHeader

Send-E-forward - MessageHeader

Send-E-forward - Patient

Send-E-forward - Patient

Send-E-forward - Provenance

Send-E-forward - Provenance

Send-E-forward - Provenance

Send-E-forward - Provenance

Send-E-forward - Receiver

Send-E-forward - Receiver

Send-E-forward - Sender

Send-E-forward - Sender

Send-E-forward - practitioner

Send-E-forward - practitioner

Send-E-forward - practitioner

Send-E-forward - practitioner

Send-E-forward - practitionerRole

Send-E-forward - practitionerRole

Send-E-forward - practitionerRole

Send-E-forward - practitionerRole

Send-F-new

Send-F-new

Send-Tek-A-new

Send-Tek-A-new

Send-Tek-A-new - Communication

Send-Tek-A-new - Communication

Send-Tek-A-new - Encounter

Send-Tek-A-new - Encounter

Send-Tek-A-new - MessageHeader

Send-Tek-A-new - MessageHeader

Send-Tek-A-new - Patient

Send-Tek-A-new - Patient

Send-Tek-A-new - Provenance

Send-Tek-A-new - Provenance

Send-Tek-A-new - Receiver

Send-Tek-A-new - Receiver

Send-Tek-A-new - Sender

Send-Tek-A-new - Sender

Send-Tek-A-new - practitioner

Send-Tek-A-new - practitioner

Send-Tek-A-new - practitionerRole

Send-Tek-A-new - practitionerRole

Send-Tek-B-new

Send-Tek-B-new

Send-Tek-B-new - Communication

Send-Tek-B-new - Communication

Send-Tek-B-new - Encounter

Send-Tek-B-new - Encounter

Send-Tek-B-new - MessageHeader

Send-Tek-B-new - MessageHeader

Send-Tek-B-new - Patient

Send-Tek-B-new - Patient

Send-Tek-B-new - Provenance

Send-Tek-B-new - Provenance

Send-Tek-B-new - Receiver

Send-Tek-B-new - Receiver

Send-Tek-B-new - Sender

Send-Tek-B-new - Sender

Send-Tek-B-new - practitioner

Send-Tek-B-new - practitioner

Send-Tek-B-new - practitionerRole

Send-Tek-B-new - practitionerRole

Send-Tek-C-new

Send-Tek-C-new

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

Simple practitioner with a name

receive-C-forward-receive_C-forward

receive_C-forward

receive-Tek-CPR-1 - New CareCommunication message

receive-Tek-CPR-1 - New CareCommunication message

receive-Tek-CPR-2 - New CareCommunication message

receive-Tek-CPR-2 - New CareCommunication message

receive-Tek-CPR-3 - New CareCommunication message

receive-Tek-CPR-3 - New CareCommunication message

receive-Tek-G

receive-Tek-G

receive-Tek-G - Communication

receive-Tek-G - Communication

receive-Tek-G - MessageHeader

receive-Tek-G - MessageHeader

receive-Tek-G - Patient

receive-Tek-G - Patient

receive-Tek-G - Provenance

receive-Tek-G - Provenance

receive-Tek-G - Receiver

receive-Tek-G - Receiver

receive-Tek-G - Sender

receive-Tek-G - Sender

receive-Tek-G - practitioner

receive-Tek-G - practitioner

receive-Tek-G - practitionerRole

receive-Tek-G - practitionerRole

receive-Tek-H - Instance of Communication resource used in a reply message.

receive-Tek-H - Content of care communication message. Valid only if used in a bundle (message) - reply message

receive-Tek-H - Instance of a MessageHeader resource used in a reply message.

receive-Tek-H - Example of a MessageHeader in a reply CareCommunication message. Valid only if used in a bundle (message).

receive-Tek-H - Reply CareCommunication message

receive-Tek-H - Example of a reply to a CareCommunication message.

receive-Tek-I - Example of a reciever organization with a SOR and an EAN identifier.

receive-Tek-I - Example of an organization with a SOR and an EAN identifier.

receive-Tek-I - Example of a sender organization with a SOR and an EAN identifier.

receive-Tek-I - Example of an organization with a SOR and an EAN identifier.

receive-Tek-I - Instance of Communication resource used in a new message.

receive-Tek-I - Content of care communication message. Valid only if used in a bundle (message) - new message

receive-Tek-I - Instance of a MessageHeader resource used in a new message.

receive-Tek-I - Example of a MessageHeader in a new CareCommunication message. Valid only if used in a bundle (message).

receive-Tek-I - New CareCommunication message.

receive-Tek-I - Example of a CareCommunication new message.

receive-Tek-I - Peter Hansen

receive-Tek-I - Patient described with minimal information. Valid only if used in a Bundle.

receive-Tek-J-duplicate

receive-Tek-J-duplicate

receive-Tek-J-duplicate - Communication

receive-Tek-J-duplicate - Communication

receive-Tek-J-duplicate - MessageHeader

receive-Tek-J-duplicate - MessageHeader

receive-Tek-J-duplicate - Patient

receive-Tek-J-duplicate - Patient

receive-Tek-J-duplicate - Provenance

receive-Tek-J-duplicate - Provenance

receive-Tek-J-duplicate - Receiver

receive-Tek-J-duplicate - Receiver

receive-Tek-J-duplicate - Sender

receive-Tek-J-duplicate - Sender

receive-Tek-J-duplicate - practitioner

receive-Tek-J-duplicate - practitioner

receive-Tek-J-duplicate - practitionerRole

receive-Tek-J-duplicate - practitionerRole

receive-Tek-K-dublicate

receive-Tek-K-dublicate

receive-Tek-M-new-dublicate-inv

receive-Tek-M-new-dublicate-inv

receive-Tek-M-new-dublicate-inv - Communication

receive-Tek-M-new-dublicate-inv - Communication

receive-Tek-M-new-dublicate-inv - MessageHeader

receive-Tek-M-new-dublicate-inv - MessageHeader

receive-Tek-M-new-dublicate-inv - Patient

receive-Tek-M-new-dublicate-inv - Patient

receive-Tek-M-new-dublicate-inv - Provenance

receive-Tek-M-new-dublicate-inv - Provenance

receive-Tek-M-new-dublicate-inv - Receiver

receive-Tek-M-new-dublicate-inv - Receiver

receive-Tek-M-new-dublicate-inv - Sender

receive-Tek-M-new-dublicate-inv - Sender

receive-Tek-M-new-dublicate-inv - practitioner

receive-Tek-M-new-dublicate-inv - practitioner

receive-Tek-M-new-dublicate-inv - practitionerRole

receive-Tek-M-new-dublicate-inv - practitionerRole

receive-Tek-N-dublicate-invalid

receive-Tek-N-dublicate-invalid

receive-Tek-O-invalid

receive-Tek-O-invalid

receive-Tek-O-invalid - Communication

receive-Tek-O-invalid - Communication

receive-Tek-O-invalid - MessageHeader

receive-Tek-O-invalid - MessageHeader

receive-Tek-O-invalid - Patient

receive-Tek-O-invalid - Patient

receive-Tek-O-invalid - Provenance

receive-Tek-O-invalid - Provenance

receive-Tek-O-invalid - Receiver

receive-Tek-O-invalid - Receiver

receive-Tek-O-invalid - Sender

receive-Tek-O-invalid - Sender

receive-Tek-O-invalid - practitioner

receive-Tek-O-invalid - practitioner

receive-Tek-O-invalid - practitionerRole

receive-Tek-O-invalid - practitionerRole

receive_A-new

receive_A-new

receive_A-new - Communication

receive_A-new - Communication

receive_A-new - MessageHeader

receive_A-new - MessageHeader

receive_A-new - Patient

receive_A-new - Patient

receive_A-new - Provenance

receive_A-new - Provenance

receive_A-new - Receiver

receive_A-new - Receiver

receive_A-new - Sender

receive_A-new - Sender

receive_A-new - Sender Careteam

receive_A-new - Sender Careteam

receive_A-new - practitioner

receive_A-new - practitioner

receive_A-new - practitionerRole

receive_A-new - practitionerRole

receive_A-new - specifik Receiver practitioner

receive_A-new - specifik Receiver practitioner

receive_A-new - specifik Receiver practitionerRole

receive_A-new - specifik Receiver practitionerRole

receive_B-reply

receive_B-reply

receive_B-reply

receive_B-reply

receive_B-reply

receive_B-reply

receive_B-reply

receive_B-reply

receive_B-reply

receive_B-reply

receive_C-forward

receive_C-forward

receive_C-forward

receive_C-forward

receive_C-forward

receive_C-forward

receive_C-forward - Patient

receive_C-forward - Patient

receive_C-forward - Provenance

receive_C-forward - Provenance

receive_C-forward - Receiver

receive_C-forward - Receiver

receive_C-forward - Sender

receive_C-forward - Sender

receive_C-forward - practitioner

receive_C-forward - practitioner

receive_C-forward - practitionerRole

receive_C-forward - practitionerRole

receive_Tek-L-dublicate

receive_Tek-L-dublicate

receive_Tek-L-dublicate - Communication

receive_Tek-L-dublicate - Communication

receive_Tek-L-dublicate - MessageHeader

receive_Tek-L-dublicate - MessageHeader

receive_Tek-L-dublicate - Patient

receive_Tek-L-dublicate - Patient

receive_Tek-L-dublicate - Provenance

receive_Tek-L-dublicate - Provenance

receive_Tek-L-dublicate - Receiver

receive_Tek-L-dublicate - Receiver

receive_Tek-L-dublicate - Sender

receive_Tek-L-dublicate - Sender

receive_Tek-L-dublicate - practitioner

receive_Tek-L-dublicate - practitioner

receive_Tek-L-dublicate - practitionerRole

receive_Tek-L-dublicate - practitionerRole

send-Tek-CPR-1 - Example of Communication

send-Tek-CPR-1 - Example of Communication

send-Tek-CPR-1 - Example of MessageHeader

send-Tek-CPR-1 - Example of MessageHeader

send-Tek-CPR-1 - Example of Patient

send-Tek-CPR-1 - Example of Patient

send-Tek-CPR-1 - Example of Provenance

send-Tek-CPR-1 - Example of Provenance

send-Tek-CPR-1 - Example of a receiver organization with a SOR and an EAN identifier.

send-Tek-CPR-1 - Example of an organization with a SOR and an EAN identifier.

send-Tek-CPR-1 - Example of a sender organization with a SOR and an EAN identifier.

send-Tek-CPR-1 - Example of an organization with a SOR and an EAN identifier.

send-Tek-CPR-1 - Example of practitioner

send-Tek-CPR-1 - practitioner

send-Tek-CPR-1 - Example of practitionerRole

send-Tek-CPR-1 - practitionerRole

send-Tek-CPR-1 - New CareCommunication message

send-Tek-CPR-1 - New CareCommunication message

send-Tek-CPR-2 - Example of Communication

send-Tek-CPR-2 - Example of Communication

send-Tek-CPR-2 - Example of MessageHeader

send-Tek-CPR-2 - Example of MessageHeader

send-Tek-CPR-2 - Example of Patient

send-Tek-CPR-2 - Example of Patient

send-Tek-CPR-2 - Example of Provenance

send-Tek-CPR-2 - Example of Provenance

send-Tek-CPR-2 - Example of a receiver organization with a SOR and an EAN identifier.

send-Tek-CPR-2 - Example of an organization with a SOR and an EAN identifier.

send-Tek-CPR-2 - Example of a sender organization with a SOR and an EAN identifier.

send-Tek-CPR-2 - Example of an organization with a SOR and an EAN identifier.

send-Tek-CPR-2 - Example of practitioner

send-Tek-CPR-2 - practitioner

send-Tek-CPR-2 - Example of practitionerRole

send-Tek-CPR-2 - practitionerRole

send-Tek-CPR-2 - New CareCommunication message

send-Tek-CPR-2 - New CareCommunication message

send-Tek-CPR-3 - Example of Communication

send-Tek-CPR-3 - Example of Communication

send-Tek-CPR-3 - Example of MessageHeader

send-Tek-CPR-3 - Example of MessageHeader

send-Tek-CPR-3 - Example of Patient

send-Tek-CPR-3 - Example of Patient

send-Tek-CPR-3 - Example of Provenance

send-Tek-CPR-3 - Example of Provenance

send-Tek-CPR-3 - Example of a receiver organization with a SOR and an EAN identifier.

send-Tek-CPR-3 - Example of an organization with a SOR and an EAN identifier.

send-Tek-CPR-3 - Example of a sender organization with a SOR and an EAN identifier.

send-Tek-CPR-3 - Example of an organization with a SOR and an EAN identifier.

send-Tek-CPR-3 - Example of practitioner

send-Tek-CPR-3 - practitioner

send-Tek-CPR-3 - Example of practitionerRole

send-Tek-CPR-3 - practitionerRole

send-Tek-CPR-3 - New CareCommunication message

send-Tek-CPR-3 - New CareCommunication message