Termx: (69 methods) CodeSystem$validate-code <in> <out> CodeSystem$validate-code_2 <in> <out> CodeSystem$compare <in> <out> CodeSystem$compare_2 <in> <out> ProvenanceSearch <in> <out> CodeSystem$sync <in> <out> CodeSystem$sync_2 <in> <out> ConceptMap <in> <out> CodeSystem$sync_3 <in> <out> CodeSystem$sync_4 <in> <out> CodeSystem$lookup <in> <out> CodeSystem$lookup_2 <in> <out> CodeSystem$subsumes <in> <out> CodeSystem$subsumes_2 <in> <out> ConceptMap$translate <in> <out> ConceptMap$translate_2 <in> <out> Provenance <in> <out> CodeSystem <in> <out> CodeSystem_2 <in> <out> ValueSet$validate-code <in> <out> ValueSet$validate-code_2 <in> <out> CodeSystem$compare_3 <in> <out> CodeSystem$compare_4 <in> <out> ConceptMap$sync <in> <out> ConceptMap$sync_2 <in> <out> StructureMapSearch <in> <out> Metadata <in> <out> ValueSet <in> <out> ValueSet_2 <in> <out> ValueSet$sync <in> <out> ValueSet$sync_2 <in> <out> ConceptMapSearch <in> <out> CodeSystem$subsumes_3 <in> <out> CodeSystem$subsumes_4 <in> <out> StructureMap$transform <in> <out> StructureMap$transform_2 <in> <out> ValueSetSearch <in> <out> ValueSet$expand <in> <out> ValueSet$expand_2 <in> <out> ValueSet$sync_3 <in> <out> ValueSet$sync_4 <in> <out> ConceptMap$sync_3 <in> <out> ConceptMap$sync_4 <in> <out> CodeSystem$validate-code_3 <in> <out> CodeSystem$validate-code_4 <in> <out> ValueSet_3 <in> <out> ValueSet_4 <in> <out> ValueSet$validate-code_3 <in> <out> ValueSet$validate-code_4 <in> <out> StructureMap <in> <out> StructureMap_2 <in> <out> ValueSet$expand_3 <in> <out> ValueSet$expand_4 <in> <out> CodeSystem$find-matches <in> <out> CodeSystem$find-matches_2 <in> <out> ConceptMap$translate_3 <in> <out> ConceptMap$translate_4 <in> <out> CodeSystem$lookup_3 <in> <out> CodeSystem$lookup_4 <in> <out> CodeSystem_3 <in> <out> CodeSystem_4 <in> <out> CodeSystemSearch <in> <out> ConceptMap_2 <in> <out> ConceptMap_3 <in> <out> StructureMap_3 <in> <out> StructureMap$transform_3 <in> <out> StructureMap$transform_4 <in> <out> CodeSystem$find-matches_3 <in> <out> CodeSystem$find-matches_4 <in> <out>🔗CodeSystem$compare_3_Input(xsd)= <The system in which composition is to be performed. This must be provided unless the operation is invoked on a code system instance
system:string>? <The version A of the system
versionA:string>? <The version B of the system
versionB:string>? 🔗CodeSystem$compare_Input(xsd)= <Resource Id
id:string> 🔗CodeSystem$find-matches_3_Input(xsd)= <One or more properties that contain information to be composed into the code
property:string>? <Whether the operation is being used by a human ('false'), or a machine ('true'). If the operation is being used by a human, the terminology server can return a list of possible matches, with commentary. For a machine, the server returns complete or partial matches, not possible matches. The default value is 'false'
exact:string>? <Resource Id
id:string> 🔗CodeSystem$find-matches_Input(xsd)= <The system in which composition is to be performed. This must be provided unless the operation is invoked on a code system instance
system:string>? <The version of the system for the inferencing to be performed
version:string>? <One or more properties that contain information to be composed into the code
property:string>? <Whether the operation is being used by a human ('false'), or a machine ('true'). If the operation is being used by a human, the terminology server can return a list of possible matches, with commentary. For a machine, the server returns complete or partial matches, not possible matches. The default value is 'false'
exact:string>? 🔗CodeSystem$lookup_3_Input(xsd)= <The code that is to be located. If a code is provided, a system must be provided
code:string>? <The system for the code that is to be located
system:string>? <The version of the system, if one was provided in the source data
version:string>? <The date for which the information should be returned. Normally, this is the current conditions (which is the default value) but under some circumstances, systems need to acccess this information as it would have been in the past. A typical example of this would be where code selection is constrained to the set of codes that were available when the patient was treated, not when the record is being edited. Note that which date is appropriate is a matter for implementation policy.
date:string>? <A property that the client wishes to be returned in the output. If no properties are specified, the server chooses what to return. The following properties are defined for all code systems: name, version (code system info) and code information: display, designation, and lang.X where X is a designation language code. These properties are returned explicitly in named out parameters with matching names, or in designations. In addition, any property codes defined by this specification or by the CodeSystem (CodeSystem.property.code) are allowed, and these are returned in the out parameter
property:string>? 🔗CodeSystem$lookup_Input(xsd)= <propertyThe code that is to be located. If a code is provided, a system must be provided
code:string>? <The date for which the information should be returned. Normally, this is the current conditions (which is the default value) but under some circumstances, systems need to acccess this information as it would have been in the past. A typical example of this would be where code selection is constrained to the set of codes that were available when the patient was treated, not when the record is being edited. Note that which date is appropriate is a matter for implementation policy.
date:string>? <A property that the client wishes to be returned in the output. If no properties are specified, the server chooses what to return. The following properties are defined for all code systems: name, version (code system info) and code information: display, designation, and lang.X where X is a designation language code. These properties are returned explicitly in named out parameters with matching names, or in designations. In addition, any property codes defined by this specification or by the CodeSystem (CodeSystem.property.code) are allowed, and these are returned in the out parameter
property:string>? <propertyResource Id
id:string> 🔗CodeSystem$subsumes_3_Input(xsd)= <The "A" code that is to be tested. If a code is provided, a system must be provided
codeA:string>? <The "B" code that is to be tested. If a code is provided, a system must be provided
codeB:string>? <Resource Id
id:string> 🔗CodeSystem$subsumes_Input(xsd)= <The "A" code that is to be tested. If a code is provided, a system must be provided
codeA:string>? <The "B" code that is to be tested. If a code is provided, a system must be provided
codeB:string>? <The code system in which subsumption testing is to be performed. This must be provided unless the operation is invoked on a code system instance
system:string>? <The version of the code system, if one was provided in the source data
version:string>? 🔗CodeSystem$sync_3_Input(xsd)= <resources:string>? <Resource Id
id:string> 🔗CodeSystem$sync_Input(xsd)= <resources:string>? 🔗CodeSystem$validate-code_3_Input(xsd)= <CodeSystem URL. The server must know the code system (e.g. it is defined explicitly in the server'scode systems, or it is known implicitly by the server
url:string>? <The code that is to be validated
code:string>? <The version of the code system, if one was provided in the source data
version:string>? <The display associated with the code, if provided. If a display is provided a code must be provided. If no display is provided, the server cannot validate the display value, but may choose to return a recommended display name in an extension in the outcome. Whether displays are case sensitive is code system dependent
display:string>? 🔗CodeSystem$validate-code_Input(xsd)= <The code that is to be validated
code:string>? <The display associated with the code, if provided. If a display is provided a code must be provided. If no display is provided, the server cannot validate the display value, but may choose to return a recommended display name in an extension in the outcome. Whether displays are case sensitive is code system dependent
display:string>? <Resource Id
id:string> 🔗CodeSystem_3_Input(xsd)= <_count:string>? <_page:string>? <The ID of the resource
_id:string>? <system:string>? <url:string>? <version:string>? <name:string>? <title:string>? <status:string>? <publisher:string>? <description:string>? <content-mode:string>? <code:string>? <identifier:string>? <date:string>? 🔗CodeSystem_Input(xsd)= <Resource Id
id:string> 🔗CodeSystemSearch_Input(xsd)= <_count:string>? <_page:string>? <The ID of the resource
_id:string>? <system:string>? <url:string>? <version:string>? <name:string>? <title:string>? <status:string>? <publisher:string>? <description:string>? <content-mode:string>? <code:string>? <identifier:string>? <date:string>? 🔗ConceptMap$sync_3_Input(xsd)= <resources:string>? <Resource Id
id:string> 🔗ConceptMap$sync_Input(xsd)= <resources:string>? 🔗ConceptMap$translate_3_Input(xsd)= <A canonical URL for a concept map. The server must know the concept map (e.g. it is defined explicitly in the server's concept maps, or it is defined implicitly by some code system known to the server.
url:string>? <The code that is to be translated. If a code is provided, a system must be provided
sourceCode:string>? <The system for the code that is to be translated
system:string>? <A coding to translate
sourceCoding:string>? <A full codeableConcept to validate. The server can translate any of the coding values (e.g. existing translations) as it chooses
sourceCodeableConcept:string>? <The target code that is to be translated to. If a code is provided, a system must be provided
targetCode:string>? <identifies a target code system in which a mapping is sought. This parameter is an alternative to the targetScope parameter - only one is required. Searching for any translation to a target code system irrespective of the context (e.g. target valueset) may lead to unsafe results, and it is at the discretion of the server to decide when to support this operation
targetSystem:string>? <A target coding to translate to
targetCoding:string>? <A full codeableConcept to validate. The server can translate any of the coding values (e.g. existing translations) as it chooses
targetCodeableConcept:string>? 🔗ConceptMap$translate_Input(xsd)= <The code that is to be translated. If a code is provided, a system must be provided
sourceCode:string>? <The system for the code that is to be translated
system:string>? <A coding to translate
sourceCoding:string>? <A full codeableConcept to validate. The server can translate any of the coding values (e.g. existing translations) as it chooses
sourceCodeableConcept:string>? <The target code that is to be translated to. If a code is provided, a system must be provided
targetCode:string>? <identifies a target code system in which a mapping is sought. This parameter is an alternative to the targetScope parameter - only one is required. Searching for any translation to a target code system irrespective of the context (e.g. target valueset) may lead to unsafe results, and it is at the discretion of the server to decide when to support this operation
targetSystem:string>? <A target coding to translate to
targetCoding:string>? <A full codeableConcept to validate. The server can translate any of the coding values (e.g. existing translations) as it chooses
targetCodeableConcept:string>? <Resource Id
id:string> 🔗ConceptMap_2_Input(xsd)= <Resource Id
id:string> 🔗ConceptMap_Input(xsd)= <_count:string>? <_page:string>? <The ID of the resource
_id:string>? <url:string>? <version:string>? <name:string>? <title:string>? <status:string>? <publisher:string>? <description:string>? <identifier:string>? <date:string>? <source-code:string>? <target-code:string>? 🔗ConceptMapSearch_Input(xsd)= <_count:string>? <_page:string>? <The ID of the resource
_id:string>? <url:string>? <version:string>? <name:string>? <title:string>? <status:string>? <publisher:string>? <description:string>? <identifier:string>? <date:string>? <source-code:string>? <target-code:string>? 🔗empty(xsd)= <empty> 🔗FHIR Resource
fhir_Resource(src)= <empty> 🔗Provenance_Input(xsd)= <target:string>? 🔗ProvenanceSearch_Input(xsd)= <target:string>? 🔗RawData(xsd)= <Bytes:base64Binary>? 🔗StructureMap$transform_3_Input(xsd)= <The structure map to apply. This is only needed if the operation is invoked at the resource level and no structureMap has been provided. If the $transform operation is invoked on a particular structure map, this will be ignored by the server
source:string>? <The logical content to transform
content:string>? 🔗StructureMap$transform_Input(xsd)= <The logical content to transform
content:string>? <Resource Id
id:string> 🔗StructureMap_3_Input(xsd)= <Resource Id
id:string> 🔗StructureMap_Input(xsd)= <_count:string>? <_page:string>? <The ID of the resource
_id:string>? <url:string>? <description:string>? <title:string>? <status:string>? 🔗StructureMapSearch_Input(xsd)= <_count:string>? <_page:string>? <The ID of the resource
_id:string>? <url:string>? <description:string>? <title:string>? <status:string>? 🔗ValueSet$expand_3_Input(xsd)= <Resource Id
id:string> 🔗ValueSet$expand_Input(xsd)= <A canonical reference to a value set. The server must know the value set (e.g. it is defined explicitly in the server's value sets, or it is defined implicitly by some code system known to the server
url:string>? <The identifier that is used to identify a specific version of the value set to be used when generating the expansion. This is an arbitrary value managed by the value set author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available.
valueSetVersion:string>? 🔗ValueSet$sync_3_Input(xsd)= <resources:string>? <Resource Id
id:string> 🔗ValueSet$sync_Input(xsd)= <resources:string>? 🔗ValueSet$validate-code_3_Input(xsd)= <Value set Canonical URL. The server must know the value set (e.g. it is defined explicitly in the server's value sets, or it is defined implicitly by some code system known to the server
url:string>? <The identifier that is used to identify a specific version of the value set to be used when validating the code. This is an arbitrary value managed by the value set author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available.
valueSetVersion:string>? <The code that is to be validated. If a code is provided, a system or a context must be provided (if a context is provided, then the server SHALL ensure that the code is not ambiguous without a system)
code:string>? <The system for the code that is to be validated
system:string>? <The version of the system, if one was provided in the source data
systemVersion:string>? <The display associated with the code, if provided. If a display is provided a code must be provided. If no display is provided, the server cannot validate the display value, but may choose to return a recommended display name using the display parameter in the outcome. Whether displays are case sensitive is code system dependent
display:string>? <A coding to validate
coding:string>? <A full codeableConcept to validate. The server returns true if one of the coding values is in the value set, and may also validate that the codings are not in conflict with each other if more than one is present
codeableConcept:string>? 🔗ValueSet$validate-code_Input(xsd)= <The code that is to be validated. If a code is provided, a system or a context must be provided (if a context is provided, then the server SHALL ensure that the code is not ambiguous without a system)
code:string>? <The system for the code that is to be validated
system:string>? <The version of the system, if one was provided in the source data
systemVersion:string>? <The display associated with the code, if provided. If a display is provided a code must be provided. If no display is provided, the server cannot validate the display value, but may choose to return a recommended display name using the display parameter in the outcome. Whether displays are case sensitive is code system dependent
display:string>? <A coding to validate
coding:string>? <A full codeableConcept to validate. The server returns true if one of the coding values is in the value set, and may also validate that the codings are not in conflict with each other if more than one is present
codeableConcept:string>? <Resource Id
id:string> 🔗ValueSet_3_Input(xsd)= <Resource Id
id:string> 🔗ValueSet_Input(xsd)= <_count:string>? <_page:string>? <The ID of the resource
_id:string>? <version:string>? <url:string>? <name:string>? <title:string>? <status:string>? <reference:string>? <publisher:string>? <description:string>? <code:string>? <identifier:string>? <date:string>? 🔗ValueSetSearch_Input(xsd)= <_count:string>? <_page:string>? <The ID of the resource
_id:string>? <version:string>? <url:string>? <name:string>? <title:string>? <status:string>? <reference:string>? <publisher:string>? <description:string>? <code:string>? <identifier:string>? <date:string>?