small changes for Pub Prev RO doc

Author: JanSchietse

articles/azure-health-insights/radiology-insights/TOC.yml

@@ -15,7 +15,7 @@ items:
     - name: Transparency note for Radiology Insights
       href: transparency-note.md
     - name: Data, privacy, and security
-      href: /azure/azure-health-insights/responsible-ai/data-privacy-security?toc=/azure/azure-health-insights/oncophenotype/toc.json
+      href: /azure/azure-health-insights/responsible-ai/data-privacy-security?toc=/azure/azure-health-insights/radiology-insights/toc.json
 - name: Concepts
   items:
      - name: Model configuration
@@ -25,7 +25,7 @@ items:
 - name: Reference
   items:
      - name: REST API
-       href: /rest/api/cognitiveservices/healthinsights/radiologyinsights
+       href: /rest/api/cognitiveservices/healthinsights/radiology-insights
      - name: SDKs
        items:
          - name: .NET

articles/azure-health-insights/radiology-insights/get-started.md

@@ -28,7 +28,7 @@ The Service URL to access your service is: https://```YOUR-NAME```.cognitiveserv
 
 To send an API request, you need your Azure AI services account endpoint and key. 
 
-You can find a full view of the [request parameters here](/rest/api/cognitiveservices/healthinsights/onco-phenotype/create-job).
+You can find a full view of the [request parameters here](/rest/api/cognitiveservices/healthinsights/radiology-insights/create-job).
 
 ![[Screenshot of the Keys and Endpoints for the Radiology Insights.](../media/keys-and-endpoints.png)](../media/keys-and-endpoints.png#lightbox)
 
@@ -124,7 +124,7 @@ Ocp-Apim-Subscription-Key: {cognitive-services-account-key}
 }
 ```
 
-You can also find a full view of the [request parameters here](/rest/api/cognitiveservices/healthinsights/onco-phenotype/create-job).
+You can also find a full view of the [request parameters here](/rest/api/cognitiveservices/healthinsights/radiology-insights/create-job).
 
 ### Evaluating a response that contains a case
 

articles/azure-health-insights/radiology-insights/inferences.md

@@ -14,7 +14,7 @@ ms.author: JanSchietse
 
 # Inference information
 
-This document describes details of all inferences generated by application of RI to a radiology document.
+This document describes the details of all inferences generated by application of RI to a radiology document.
 
 The Radiology Insights feature of Azure Health Insights uses natural language processing techniques to process unstructured medical radiology documents. It adds several types of inferences that help the user to effectively monitor, understand, and improve financial and clinical outcomes in a radiology workflow context.
 
@@ -63,10 +63,12 @@ To interact with the Radiology-Insights model, you can provide several model con
 An age mismatch occurs when the document gives a certain age for the patient, which differs from the age that is calculated based on the patient’s info birthdate and the encounter period in the request.  
 - kind: RadiologyInsightsInferenceType.AgeMismatch;
 
-<details><summary>Examples request/response json</summary>
+Examples request/response json:
+
 [!INCLUDE [Example input json](../includes/example-inference-age-mismatch-json-request.md)]
+
 [!INCLUDE [Example output json](../includes/example-inference-age-mismatch-json-response.md)]
-</details>
+
 
 
 
@@ -96,10 +98,12 @@ The meaning of this field is as follows:
 A mismatch with discrepancy type “textLaterityMissing” has no token extensions.
 
 
-<details><summary>Examples request/response json</summary>
+Examples request/response json:
+
 [!INCLUDE [Example input json](../includes/example-inference-laterality-discrepancy-json-request.md)]
+
 [!INCLUDE [Example output json](../includes/example-inference-laterality-discrepancy-json-response.md)]
-</details>
+
 
 
 
@@ -112,10 +116,12 @@ Field “sexIndication” contains one coding with a SNOMED concept for either M
 - 248152002: FEMALE (FINDING)
 
 
-<details><summary>Examples request/response json</summary>
+Examples request/response json:
+
 [!INCLUDE [Example input json](../includes/example-inference-sex-mismatch-json-request.md)]
+
 [!INCLUDE [Example output json](../includes/example-inference-sex-mismatch-json-response.md)]
-</details>
+
 
 
 
@@ -137,10 +143,12 @@ Fields “missingBodyParts” and/or “missingBodyPartsMeasurements” contain
 
 
 
-<details><summary>Examples request/response json</summary>
+Examples request/response json:
+
 [!INCLUDE [Example input json](../includes/example-inference-complete-order-discrepancy-json-request.md)]
+
 [!INCLUDE [Example output json](../includes/example-inference-complete-order-discrepancy-json-response.md)]
-</details>
+
 
 
 
@@ -162,10 +170,12 @@ Field “ordertype” contains one Coding, with one of the following Loinc codes
 Fields “presentBodyParts” and/or “presentBodyPartsMeasurements” contain body parts (radlex codes) that are present or whose measurements are present. The token extensions refer to body parts or measurements that are present (or words that imply them).
 
 
-<details><summary>Examples request/response json</summary>
+Examples request/response json:
+
 [!INCLUDE [Example input json](../includes/example-inference-limited-order-discrepancy-json-request.md)]
+
 [!INCLUDE [Example output json](../includes/example-inference-limited-order-discrepancy-json-response.md)]
-</details>
+
 
 
 
@@ -204,12 +214,6 @@ list of fields within field “finding”, except “component”:
 
 In this list, the string before the colon is the code, and the string after the colon is the display name.
 If the value is “NONE (QUALIFIER VALUE)”, the finding is absent. This value is, for example, “no sepsis”.
-category: if filled, this field contains an array with one element. It contains one of the following SNOMED concepts:
-- 439401001: DIAGNOSIS (OBSERVABLE ENTITY)
-- 404684003: CLINICAL FINDING (FINDING)
-- 162432007: SYMPTOM: GENERALIZED (FINDING)
-- 246501002: TECHNIQUE (ATTRIBUTE)
-- 91722005: PHYSICAL ANATOMICAL ENTITY (BODY STRUCTURE)
 
 code: 
 - SNOMED code 404684003: CLINICAL FINDING (FINDING) (meaning that the finding has a clinical indicator) 
@@ -278,10 +282,12 @@ If “valueQuantity” is set, then “valueQuantity.value” is always set. In
 If “valueRange” is set, then “valueRange.low” and “valueRange.high” are set to quantities with the same data as described in the previous paragraph. This field contains, for example, “The tumor is between 2.5 cm and 2.6 cm in size".
 
 
-<details><summary>Examples request/response json</summary>
+Examples request/response json:
+
 [!INCLUDE [Example input json](../includes/example-inference-finding-json-request.md)]
+
 [!INCLUDE [Example output json](../includes/example-inference-finding-json-response.md)]
-</details>
+
 
 
 
@@ -296,10 +302,12 @@ Field “result.finding”, if set, contains the same information as the “find
 Next to token extensions, there can be an extension for a section. This field contains the most specific section that the first token of the critical result is in (or to be precise, the first token that is in a section). This section is in the same format as a section for a finding.
 
 
-<details><summary>Examples request/response json</summary>
+Examples request/response json:
+
 [!INCLUDE [Example input json](../includes/example-inference-critical-result-json-request.md)]
+
 [!INCLUDE [Example output json](../includes/example-inference-critical-result-json-response.md)]
-</details>
+
 
 
 
@@ -357,10 +365,12 @@ This type has the following fields, the first 2 of which are always filled:
 - “view”: not set.
 
 
-<details><summary>Examples request/response json</summary>
+Examples request/response json:
+
 [!INCLUDE [Example input json](../includes/example-1-inference-follow-up-recommendation-json-request.md)]
+
 [!INCLUDE [Example output json](../includes/example-1-inference-follow-up-recommendation-json-response.md)]
-</details>
+
 
 
 
@@ -374,10 +384,12 @@ This inference is created when findings or test results were communicated to a m
 
 Field “wasAcknowledged” is set to true if the communication was verbal (nonverbal communication might not have reached the recipient yet and cannot be considered acknowledged). Field “dateTime” is set if the date-time of the communication is known. Field “recipient” is set if the recipient(s) are known. See the OpenAPI spec for its possible values.
 
-<details><summary>Examples request/response json</summary>
+Examples request/response json:
+
 [!INCLUDE [Example input json](../includes/example-inference-follow-up-communication-json-request.md)]
+
 [!INCLUDE [Example output json](../includes/example-inference-follow-up-communication-json-response.md)]
-</details>
+
 
 
 
@@ -394,10 +406,12 @@ Field “procedureCodes”, if set, contains LOINC codes.
 Field “orderedProcedure” contains the description(s) and the code(s) of the ordered procedure(s) as given by the client. The descriptions are in field “orderedProcedure.description”, separated by “;;”. The codes are in “orderedProcedure.code.coding”. In every coding in the array, only field “coding” is set.
 
 
-<details><summary>Examples request/response json</summary>
+Examples request/response json:
+
 [!INCLUDE [Example input json](../includes/example-inference-radiology-procedure-json-request.md)]
+
 [!INCLUDE [Example output json](../includes/example-inference-radiology-procedure-json-response.md)]
-</details>
+
 
 
 

articles/azure-health-insights/radiology-insights/model-configuration.md

@@ -66,11 +66,14 @@ false  | No Evidence is returned
     - type: boolean
     - description: Provide a single focused sentence as evidence for the recommendation, default is false.
 
-When includeEvidence is false, no evidence is returned. 
 
-This configuration overrules includeRecommendationsWithNoSpecifiedModality and provideFocusedSentenceEvidence and no evidence is shown. 
+IncludeEvidence
+
+- IncludeEvidence
+- type: boolean
+- Provide evidence for the inference, default is false, no evidence is returned.
+ 
 
-When includeEvidence is true, it depends on the value set on the two other configurations whether the evidence of the inference or a single focused sentence is given as evidence. 
 
 ## Examples 
 
@@ -86,10 +89,12 @@ As a result, the model includes evidence for all inferences.
 - The model checks for follow-up recommendations with no specific radiologic modality.
 - The model provides a single focused sentence as evidence for the recommendation. 
 
-<details><summary>Examples request/response json</summary>
+Examples request/response json:
+
 [!INCLUDE [Example input json](../includes/example-2-inference-follow-up-recommendation-json-request.md)]
+
 [!INCLUDE [Example output json](../includes/example-2-inference-follow-up-recommendation-json-response.md)]
-</details>
+
 
 
 
@@ -105,10 +110,12 @@ As a result, the model includes evidence for all inferences.
 - The model provides a single focused sentence as evidence for the finding. 
 
 
-<details><summary>Examples request/response json</summary>
+Examples request/response json:
+
 [!INCLUDE [Example input json](../includes/example-1-inference-follow-up-recommendation-json-request.md)]
+
 [!INCLUDE [Example output json](../includes/example-1-inference-follow-up-recommendation-json-response.md)]
-</details>
+