This page is part of the FHIR Specification (v3.3.0: R4 Ballot 2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R4B R4 R3
FHIR Infrastructure Work Group | Maturity Level: N/A | Ballot Status: Informative |
Definition for Code System TestScriptProfileDestinationType
<CodeSystem xmlns="http://hl7.org/fhir"> <id value="testscript-profile-destination-types"/> <meta> <lastUpdated value="2018-04-03T12:05:46.262+10:00"/> <profile value="http://hl7.org/fhir/StructureDefinition/shareablecodesystem"/> </meta> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <h2> TestScriptProfileDestinationType</h2> <div> <p> This value set defines a set of codes that are used to indicate the profile type of a test system when acting as the destination within a TestScript.</p> </div> <p> This code system http://hl7.org/fhir/testscript-profile-destination-types defines the following codes:</p> <table class="codes"> <tr> <td style="white-space:nowrap"> <b> Code</b> </td> <td> <b> Display</b> </td> <td> <b> Definition</b> </td> </tr> <tr> <td style="white-space:nowrap">FHIR-Server <a name="testscript-profile-destination-types-FHIR-Server"> </a> </td> <td> FHIR Server</td> <td> General FHIR server used to respond to operations sent from a FHIR client.</td> </tr> <tr> <td style="white-space:nowrap">FHIR-SDC-FormManager <a name="testscript-profile-destination-types-FHIR-SDC-FormManager"> </a> </td> <td> FHIR SDC FormManager</td> <td> A FHIR server acting as a Structured Data Capture Form Manager.</td> </tr> <tr> <td style="white-space:nowrap">FHIR-SDC-FormProcessor <a name="testscript-profile-destination-types-FHIR-SDC-FormProcessor"> </a> </td> <td> FHIR SDC FormProcessor</td> <td> A FHIR server acting as a Structured Data Capture Form Processor.</td> </tr> <tr> <td style="white-space:nowrap">FHIR-SDC-FormReceiver <a name="testscript-profile-destination-types-FHIR-SDC-FormReceiver"> </a> </td> <td> FHIR SDC FormReceiver</td> <td> A FHIR server acting as a Structured Data Capture Form Receiver.</td> </tr> </table> </div> </text> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg"> <valueCode value="fhir"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-ballot-status"> <valueString value="Trial Use"/> </extension> <extension url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm"> <valueInteger value="2"/> </extension> <url value="http://hl7.org/fhir/testscript-profile-destination-types"/> <identifier> <system value="urn:ietf:rfc:3986"/> <value value="urn:oid:2.16.840.1.113883.4.642.1.715"/> </identifier> <version value="3.3.0"/> <name value="TestScriptProfileDestinationType"/> <status value="draft"/> <experimental value="true"/> <publisher value="FHIR Project team"/> <contact> <telecom> <system value="url"/> <value value="http://hl7.org/fhir"/> </telecom> </contact> <description value="This value set defines a set of codes that are used to indicate the profile type of a test system when acting as the destination within a TestScript."/> <caseSensitive value="true"/> <valueSet value="http://hl7.org/fhir/ValueSet/testscript-profile-destination-types"/> <content value="complete"/> <concept> <code value="FHIR-Server"/> <display value="FHIR Server"/> <definition value="General FHIR server used to respond to operations sent from a FHIR client."/> </concept> <concept> <code value="FHIR-SDC-FormManager"/> <display value="FHIR SDC FormManager"/> <definition value="A FHIR server acting as a Structured Data Capture Form Manager."/> </concept> <concept> <code value="FHIR-SDC-FormProcessor"/> <display value="FHIR SDC FormProcessor"/> <definition value="A FHIR server acting as a Structured Data Capture Form Processor."/> </concept> <concept> <code value="FHIR-SDC-FormReceiver"/> <display value="FHIR SDC FormReceiver"/> <definition value="A FHIR server acting as a Structured Data Capture Form Receiver."/> </concept> </CodeSystem>
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.