|
|
JSON Format/PreferredId/terminology-preferred-id-get-json
|
1 |
NamingSystem $preferred-id tests against the example NamingSystem resource in the R4 specification namingsystem-example.xml. All $preferred-id operations are performed using the FHIR Operation Framework HTTP GET method. |
XML |
4 |
FHIR 4.0.1
|
|
|
JSON Format/PreferredId/terminology-preferred-id-post-parameters-json
|
1 |
NamingSystem $preferred-id tests against the example NamingSystem resource in the R4 specification namingsystem-example.xml. All $preferred-id operations are performed using the FHIR Operation Framework HTTP POST method with Parameters of id and type. |
XML |
4 |
FHIR 4.0.1
|
|
|
JSON Format/Subsumes/terminology-subsumes-snomed-01-ok-get-json
|
1 |
CodeSystem $subsumes tests against known SNOMED codes where the expected outcome is a successful response with a valid outcome code value. All $subsumes operations are performed using the FHIR Operation Framework HTTP GET method. |
XML |
4 |
FHIR 4.0.1
|
|
|
JSON Format/Subsumes/terminology-subsumes-snomed-02-ok-post-code-json
|
1 |
CodeSystem $subsumes tests against known SNOMED codes where the expected outcome is a successful response with a valid outcome code value. All $subsumes operations are performed using the FHIR Operation Framework HTTP POST method with Parameters of system, codeA and codeB. |
XML |
4 |
FHIR 4.0.1
|
|
|
JSON Format/Subsumes/terminology-subsumes-snomed-03-ok-post-coding-json
|
1 |
CodeSystem $subsumes tests against known SNOMED codes where the expected outcome is a successful response with a valid outcome code value. All $subsumes operations are performed using the FHIR Operation Framework HTTP POST method with Parameters of system, codingA and codingB. |
XML |
4 |
FHIR 4.0.1
|
|
|
JSON Format/Subsumes/terminology-subsumes-snomed-04-notok-get-json
|
1 |
CodeSystem $subsumes tests against known and unknown SNOMED codes where the expected outcome is a failure response with a returned OperationOutcome. All $subsumes operations are performed using the FHIR Operation Framework HTTP GET method. |
XML |
6 |
FHIR 4.0.1
|
|
|
JSON Format/Subsumes/terminology-subsumes-snomed-05-notok-post-code-json
|
1 |
CodeSystem $subsumes tests against known and unknown SNOMED codes where the expected outcome is a failure response with a returned OperationOutcome. All $subsumes operations are performed using the FHIR Operation Framework HTTP POST method with Parameters of system, codeA and codeB. |
XML |
6 |
FHIR 4.0.1
|
|
|
JSON Format/Subsumes/terminology-subsumes-snomed-06-notok-post-coding-json
|
1 |
CodeSystem $subsumes tests against known and unknown SNOMED codes where the expected outcome is a failure response with a returned OperationOutcome. All $subsumes operations are performed using the FHIR Operation Framework HTTP POST method with Parameters of system, codingA and codingB. |
XML |
6 |
FHIR 4.0.1
|
|
|
JSON Format/Translate/terminology-translate-01-ok-get-json
|
1 |
ConceptMap $translate tests against known FHIR code systems where the expected outcome is a successful response with a matched code value from the target system. All $translate operations are performed using the FHIR Operation Framework HTTP GET method. |
XML |
2 |
FHIR 4.0.1
|
|
|
JSON Format/Translate/terminology-translate-02-ok-post-code-json
|
1 |
ConceptMap $translate tests against known FHIR code systems where the expected outcome is a successful response with a matched code value from the target system. All $translate operations are performed using the FHIR Operation Framework HTTP POST method with Parameters of code, system, source and target. |
XML |
2 |
FHIR 4.0.1
|