-
Notifications
You must be signed in to change notification settings - Fork 0
/
ips_requirements.txt
49 lines (46 loc) · 1.5 KB
/
ips_requirements.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
ConformanceStatement
Provide Patient.operation.$summary definition
Bundle
CREATE
Search for Patient
if no patient found; CREATE patient
If bundle allready exists; overwrite
SEARCH
id
UPDATE
Check for security-label
DELETE
Check for security-label
Patient
CREATE
SEARCH
id
UPDATE
Check for security-label
DELETE
Check for security-label
EXTENSION POST $summary, GET /{$id}/$summary
Finds linked bundle
Checks for profile filter
if no bundle;
return error
Returns bundle
error possibilities
Improper Request
Handled by hapi-fhir server (OperationOutcome)
Resource not found
Handled by hapi-fhir server (OperationOutcome)
Patient has no bundle
Returns empty bundle with document narrative describing no data available, dataabsentreason in the sections as well.
DISABLE all other providers
High priority
provide summary operation
Easy create of entire bundles
Keep records fairly isolated; not dynamic for ease of testing
Keep original ids
provide security label for only our records if needed.
Our resources are read-only.
Everyone else does not get a guarentee of persistance.
Possible refresh time/rollback state?
User usecase
1) POST IPS bundle, Patient/{$id}/$summary (persist patient, persist composition, do not persist resources over the server)