Loading...

XML

Word

Printable

JSON

Specification:

US Da Vinci CDex (FHIR)
Raised in Version:

current
Work Group:

Patient Care
Related URL:
http://hl7.org/fhir/us/davinci-cdex/2021JAN/CapabilityStatement-data-consumer-server.html
Related Page(s):

Artifacts Summary
Related Section(s):
10.2
Grouping:
- Block-Vote-4
- EH-020-Ballot-Review
Resolution Description:

Hide

Add

It is up to the EHR (Data Source) to set the status of each Task as appropriate. (see the [Task state machine diagram] in the FHIR specification for more background on Task transitions).

in Requirements page in the Fetching the Data section

Show
Add It is up to the EHR (Data Source) to set the status of each Task as appropriate. (see the [Task state machine diagram] in the FHIR specification for more background on Task transitions). in Requirements page in the Fetching the Data section
Resolution Vote:
Eric Haas/Jay Lyle: 11-0-11
Change Category:
Clarification
Change Impact:
Non-substantive

When and how do data servers terminate a client's set of requests? This should not be allowed indefinitely.

(Comment 11 - imported by: Jean Duteau)

is voted on by

BALLOT-15168 Negative - Celine Lefebvre : 2021-Jan-FHIR IG CDex R1 STU

relates to

FHIR-30820 When a task is complete what triggers the termination of a payer's ability to fetch data?