Capability Statement are not well populated - need more info and standard/complete information

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • US Da Vinci CDex (FHIR)
    • Patient Care
    • STU
    • Profiles [deprecated]
    • Hide

      We will refactor the capability statements as follows:

      • One capability statement for EHRs that is based on the U.S. Core EHR capability statement that adds support for asynchronous Task-based data requests & retrieval
        • Servers SHALL support polling and SHOULD support subscription
      • One capability statement for Payers that is not based on an U.S. Core capability statement and adds support for asynchronous Task-based data requests & retrieval
        • Clients SHALL support polling and SHOULD support subscription
      • A statement indicating that client systems SHALL either comply with the CDex asynchronous capability statement or comply with the U.S. Core capability statement (for at least one resource type)

      Will enforce expectations around authentication/authorization expectations either directly or by pointing to HRex (i.e. how server-to-server will work)

      Will also ensure that the capability statements render correctly in a manner similar to SDC.

      Show
      We will refactor the capability statements as follows: One capability statement for EHRs that is based on the U.S. Core EHR capability statement that adds support for asynchronous Task-based data requests & retrieval Servers SHALL support polling and SHOULD support subscription One capability statement for Payers that is not based on an U.S. Core capability statement and adds support for asynchronous Task-based data requests & retrieval Clients SHALL support polling and SHOULD support subscription A statement indicating that client systems SHALL either comply with the CDex asynchronous capability statement or comply with the U.S. Core capability statement (for at least one resource type) Will enforce expectations around authentication/authorization expectations either directly or by pointing to HRex (i.e. how server-to-server will work) Will also ensure that the capability statements render correctly in a manner similar to SDC.
    • Bob Dieterle / Laura Herrman : 13-0-2
    • Enhancement
    • Non-compatible

      These capability statements don't seem fully formed. Is this really all they are supposed to say? There is not explanation of what they mean. The narrative explaining these needs to be improved to make them more understandable.

            Assignee:
            Unassigned
            Reporter:
            Lisa R. Nelson
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: