Jan 2015 Ballot Comment #262

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Not Persuasive
    • Priority: Medium
    • FHIR Core (FHIR)
    • DSTU1 [deprecated]
    • Security
    • Provenance
    • Hide

      The Provenance resource meets your use-case need. It is simpy technically modeled in the opposite direction. In REST this is the more usual model. Also, in REST any pointer in one direction can be traversed in the other direction through queries.

          • TODO – In the FHIR spec is an explaination of this link traversal method.
      Show
      The Provenance resource meets your use-case need. It is simpy technically modeled in the opposite direction. In REST this is the more usual model. Also, in REST any pointer in one direction can be traversed in the other direction through queries. TODO – In the FHIR spec is an explaination of this link traversal method.
    • Enhancement

      Comments
      It would be easier to create a resource intended to be associated with any resource that would specify the associated attribution and activities. For instance an observation resource could contain associated attribution and actions applied to that observation.

      Grahame's Comments
      resources are generally produced in groups. And the provenance information pertains to the group. The pattern we hve developed over several cycles, though it may not yet have been implemented enough. Still we'd want implementation experience before changing it

            Assignee:
            Unassigned
            Reporter:
            Ioana Singureanu
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: