| Evidence-Emitter-REM-SBB | EvidenceEmitter-8 | reviewed | Testable |
1
|
0
| | The [Evidence Emitter REM SBB] MUST fill the relevant audit
parameters using the values of the policy decision | 0 | | 11/13/15 3:13:38 PM by Abderrazek Boufahja |
|
| FHIR4OP | FHIR4OP-001 | reviewed | Testable |
0
|
0
| Will be constrained by the operation definition coming from the IHE profile | The body of the invocation contains a special infrastructure resource called Parameters, which represents a collection of named parameters as <key,value> pairs, where the value may be any primitive or complex datatype or even a full Resource. | 2 | Section 3.2.0.1 | 1/3/20 3:30:35 PM by Anne-Gaëlle Bergé |
|
| FHIR4OP | FHIR4OP-002 | reviewed | Testable |
0
|
0
| Will be constrained by the operation definition coming from the IHE profile | The body of the invocation may also include strings formatted as search parameter
types. | 2 | Section 3.2.0.1 | 1/3/20 3:30:35 PM by Anne-Gaëlle Bergé |
|
| FHIR4OP | FHIR4OP-003 | reviewed | Testable |
0
|
0
| Content of the Parameter resource will be constrained by the IHE profile | Upon completion, the operation returns another Parameters resource, containing one or more output parameters. | 2 | Section 3.2.0.1 | 1/3/20 3:30:35 PM by Anne-Gaëlle Bergé |
|
| FHIR4OP | FHIR4OP-004 | reviewed | Testable |
0
|
0
| Will be constrained by the operation definition coming from the IHE profile | This means that a FHIR operation can take a set of zero or more parameters in and return a set of zero or more result parameters out. | 2 | Section 3.2.0.1 | 1/3/20 3:30:35 PM by Anne-Gaëlle Bergé |
|
| FHIR4OP | FHIR4OP-005 | reviewed | Testable |
0
|
0
| | Operations may be invoked using a GET , with parameters as HTTP URL parameters, if:
1. there are only simple input parameters - i.e. no complex datatypes like 'Identifier' or 'Reference', and
2. and the operation does not affect the state of the server | 2 | Section 3.2.0.1 | 1/3/20 3:30:35 PM by Anne-Gaëlle Bergé |
|
| FHIR4OP | FHIR4OP-006 | reviewed | Testable |
0
|
0
| | If there is a single output parameter named 'return' then the response MAY be the resource that is the return value, with no Parameters resource. | 2 | Section 3.2.0.1 | 1/3/20 3:30:35 PM by Anne-Gaëlle Bergé |
|
| FHIR4OP | FHIR4OP-007 | reviewed | Testable |
0
|
0
| | If the response is a Bundle, the correct Bundle.type is 'collection', unless it has search semantics, such as matching resource counts, and page links. | 2 | Section 3.2.0.1 | 1/3/20 3:30:35 PM by Anne-Gaëlle Bergé |
|
| FHIR4OP | FHIR4OP-008 | reviewed | Testable |
0
|
0
| Might be further constrained by each IHE profile | Operations are typically executed synchronously: a client sends a request to a server that includes the operation's in parameters and the server replies with the
operation's out parameters. | 3 | Section 3.2.0.6 | 1/3/20 3:30:35 PM by Anne-Gaëlle Bergé |
|
| FHIR4OP | FHIR4OP-009 | reviewed | Testable |
0
|
0
| | When parameters have a search type, the search modifiers are available and are used on the parameter name in the Parameters resource (e.g. "code:in") | 3 | Section 3.2.0.6.1 | 1/3/20 3:30:35 PM by Anne-Gaëlle Bergé |
|
| FHIR4OP | FHIR4OP-010 | reviewed | Testable |
0
|
0
| paraphrases FHIR4OP-001 | An operation is generally invoked by performing an HTTP POST to the operation's end-point. The submitted content is the special Parameters format (the "in" parameters) - a list of named parameters. | 3 | Section 3.2.0.6.1 | 1/3/20 3:30:35 PM by Anne-Gaëlle Bergé |
|
| FHIR4OP | FHIR4OP-011 | reviewed | Testable |
0
|
0
| paraphrases FHIR4OP-005 | If all the parameters for the operation are primitive types and the operation has affectsState = false, the operation may be invoked by performing an HTTP GET operation where all of the values of the parameters are appended to the URL in the search portion of the URL (e.g. after the '?' character). Servers SHALL support this method of invocation. | 3 | Section 3.2.0.6.1 | 1/3/20 3:30:35 PM by Anne-Gaëlle Bergé |
|
| FHIR4OP | FHIR4OP-012 | reviewed | Testable |
0
|
0
| | When using the HTTP GET operation, if there is a repeating parameter for the extended operation the values for that parameter are repeated by repeating the
named parameter. | 3 | Section 3.2.0.6.1 | 1/3/20 3:30:35 PM by Anne-Gaëlle Bergé |
|
| FHIR4OP | FHIR4OP-013 | reviewed | Testable |
0
|
0
| | If, when invoking the operation, there is exactly one input parameter of type Resource (irrespective of whether other possible parameters are defined), the
operation can also be executed by a POST with that resource as the body of the request (and no parameters on the url). | 4 | Section 3.2.0.6.1 | 1/3/20 3:30:35 PM by Anne-Gaëlle Bergé |
|
| FHIR4OP | FHIR4OP-014 | reviewed | Testable |
0
|
0
| | Servers MAY choose to support submission of the parameters represented in multi-part/form-data format as well, which can be useful when testing an operation using HTML forms. | 4 | Section 3.2.0.6.1 | 1/3/20 3:30:35 PM by Anne-Gaëlle Bergé |
|
| FHIR4OP | FHIR4OP-015 | reviewed | Testable |
0
|
0
| | If an operation succeeds, an HTTP Status success code is returned. | 4 | Section 3.2.0.6.2 | 1/3/20 3:30:35 PM by Anne-Gaëlle Bergé |
|
| FHIR4OP | FHIR4OP-016 | reviewed | Testable |
0
|
0
| Preferred: might be further constrained in each IHE profile | If an operation succeds, returned status code will usually be a 2xx code, though it may also be a 303. | 4 | Section 3.2.0.6.2 | 1/3/20 3:30:35 PM by Anne-Gaëlle Bergé |
|
| FHIR4OP | FHIR4OP-017 | reviewed | Testable |
0
|
0
| | Other kinds of 3xx codes should be understood to indicate that the operation did not proceed, and the client will need to re-issue the operation if it can perform the redirection (e.g. may get redirected to an authentication step). | 4 | Section 3.2.0.6.2 | 1/3/20 3:30:35 PM by Anne-Gaëlle Bergé |
|
| FHIR4OP | FHIR4OP-018 | reviewed | Testable |
0
|
0
| | User agents should note that servers may issue redirects, etc. to authenticate the client in response to an operation request. | 4 | Section 3.2.0.6.2 | 1/3/20 3:30:35 PM by Anne-Gaëlle Bergé |
|
| FHIR4OP | FHIR4OP-019 | reviewed | Testable |
0
|
0
| | An HTTP status code of 4xx or 5xx indicates an error, and an OperationOutcome SHOULD be returned with details. | 4 | Section 3.2.0.6.2 | 1/3/20 3:30:35 PM by Anne-Gaëlle Bergé |
|