Typos in the Human exchange page

XMLWordPrintableJSON

    • Type: Technical Correction
    • Resolution: Persuasive
    • Priority: Medium
    • US Da Vinci HRex (FHIR)
    • 0.2.0 [deprecated]
    • Clinical Interoperability Council
    • Exchanges allowing human intervention [deprecated]
    • Correction

      In step 4 of section 3.7.1.2 there seems to be a typo where it says:

      Merely having the relevant records existing on the data source system sufficient to satisfy the original CommunicationRequest because the data consumer would have no way of knowing which records are pertinent to their request. 

      It should probably read:

      Merely having the relevant records existing on the data source system is not sufficient to satisfy the original CommunicationRequest because the data consumer would have no way of knowing which records are pertinent to their request. 

       

      In step 4 of section 3.7.1.2 there seems to be a typo where it says:

      However, closing the loop by formally creating a Communication instance as part of the patient record necessarily always appropriate. (Such resources will rarely be created for data shared by the data consumer directly querying the data source's system.

      It should probably read:

      However, closing the loop by formally creating a Communication instance as part of the patient record is always appropriate. (Such resources will rarely be created for data shared by the data consumer directly querying the data source's system*)*.

       

      In step 5 of section 3.7.1.2 there seems to be a typo where it says:

      Once the _data source has the Communication and knows what data is deemed to satisfy the request, it can then directly query that information - either as individual reads, as a query by resource id(s) or by a batch of queries or reads._

      It should probably read ("data source" should be "data consumer"):

      Once the _data consumer has the Communication and knows what data is deemed to satisfy the request, it can then directly query that information - either as individual reads, as a query by resource id(s) or by a batch of queries or reads._

            Assignee:
            Unassigned
            Reporter:
            Craig Newman
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: