Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-30245

Backend Service Client CapabilityStatment is confusing to read

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Making EHR Data More available for Research and Public Health (MedMorph) (FHIR)
    • 0.1.0
    • Public Health
    • MedMorph Backend Service App [deprecated]
    • Hide

      Will split the BSA capability statement to a client capability statement and a server capability statement to provide more clarity.

      Show
      Will split the BSA capability statement to a client capability statement and a server capability statement to provide more clarity.
    • Kishore Bashyam / Craig Newman : 28 - 0 - 1
    • Correction
    • Compatible, substantive

    Description

      The CapabilityStatement for the backend service application is confusing to understand from a human readable standpoint as it contains both server and client requirements and does not specify which requirements are for which context.  This page should be reformatted to make it clear which constraints go with which context or the CapabilityStatemnet should be broken up into server side and client side statements. 

      Attachments

        Activity

          People

            nageshbashyam Nagesh Bashyam
            rdingwell Rob Dingwell
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: