|
1 | 1 | Feature: Producer - createDocumentReference - Success Scenarios |
2 | 2 |
|
3 | | - # Scenario: Successfully create a Document Pointer (care plan) |
4 | | - # Given the application 'DataShare' (ID 'z00z-y11y-x22x') is registered to access the API |
5 | | - # And the organisation 'ANGY1' is authorised to access pointer types: |
6 | | - # | system | value | |
7 | | - # | http://snomed.info/sct | 736253002 | |
8 | | - # When producer 'ANGY1' creates a DocumentReference with values: |
9 | | - # | property | value | |
10 | | - # | subject | 9278693472 | |
11 | | - # | status | current | |
12 | | - # | type | 736253002 | |
13 | | - # | category | 734163000 | |
14 | | - # | custodian | ANGY1 | |
15 | | - # | author | HAR1 | |
16 | | - # | url | https://example.org/my-doc.pdf | |
17 | | - # Then the response status code is 201 |
18 | | - # And the response is an OperationOutcome with 1 issue |
19 | | - # And the OperationOutcome contains the issue: |
20 | | - # """ |
21 | | - # { |
22 | | - # "severity": "information", |
23 | | - # "code": "informational", |
24 | | - # "details": { |
25 | | - # "coding": [ |
26 | | - # { |
27 | | - # "system": "https://fhir.nhs.uk/ValueSet/NRL-ResponseCode", |
28 | | - # "code": "RESOURCE_CREATED", |
29 | | - # "display": "Resource created" |
30 | | - # } |
31 | | - # ] |
32 | | - # }, |
33 | | - # "diagnostics": "The document has been created" |
34 | | - # } |
35 | | - # """ |
36 | | - # And the response has a Location header |
37 | | - # And the Location header starts with '/producer/FHIR/R4/DocumentReference/ANGY1-' |
38 | | - # And the resource in the Location header exists with values: |
39 | | - # | property | value | |
40 | | - # | subject | 9278693472 | |
41 | | - # | status | current | |
42 | | - # | type | 736253002 | |
43 | | - # | category | 734163000 | |
44 | | - # | custodian | ANGY1 | |
45 | | - # | author | HAR1 | |
46 | | - # | url | https://example.org/my-doc.pdf | |
| 3 | + Scenario: Successfully create a Document Pointer (care plan) |
| 4 | + Given the application 'DataShare' (ID 'z00z-y11y-x22x') is registered to access the API |
| 5 | + And the organisation 'ANGY1' is authorised to access pointer types: |
| 6 | + | system | value | |
| 7 | + | http://snomed.info/sct | 736253002 | |
| 8 | + When producer 'ANGY1' creates a DocumentReference with values: |
| 9 | + | property | value | |
| 10 | + | subject | 9278693472 | |
| 11 | + | status | current | |
| 12 | + | type | 736253002 | |
| 13 | + | category | 734163000 | |
| 14 | + | custodian | ANGY1 | |
| 15 | + | author | HAR1 | |
| 16 | + | url | https://example.org/my-doc.pdf | |
| 17 | + Then the response status code is 201 |
| 18 | + And the response is an OperationOutcome with 1 issue |
| 19 | + And the OperationOutcome contains the issue: |
| 20 | + """ |
| 21 | + { |
| 22 | + "severity": "information", |
| 23 | + "code": "informational", |
| 24 | + "details": { |
| 25 | + "coding": [ |
| 26 | + { |
| 27 | + "system": "https://fhir.nhs.uk/ValueSet/NRL-ResponseCode", |
| 28 | + "code": "RESOURCE_CREATED", |
| 29 | + "display": "Resource created" |
| 30 | + } |
| 31 | + ] |
| 32 | + }, |
| 33 | + "diagnostics": "The document has been created" |
| 34 | + } |
| 35 | + """ |
| 36 | + And the response has a Location header |
| 37 | + And the Location header starts with '/producer/FHIR/R4/DocumentReference/ANGY1-' |
| 38 | + And the resource in the Location header exists with values: |
| 39 | + | property | value | |
| 40 | + | subject | 9278693472 | |
| 41 | + | status | current | |
| 42 | + | type | 736253002 | |
| 43 | + | category | 734163000 | |
| 44 | + | custodian | ANGY1 | |
| 45 | + | author | HAR1 | |
| 46 | + | url | https://example.org/my-doc.pdf | |
| 47 | + |
47 | 48 | # # NRL-766 Resolve custodian suffix issues |
48 | 49 | # Scenario: Successfully create a Document Pointer (care plan) with custodian suffix |
49 | 50 | # Given the application 'DataShare' (ID 'z00z-y11y-x22x') is registered to access the API |
|
0 commit comments