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

EndPoint.payloadType can hold FHIR canonical URI (e.g. StructureDefinition Profile)

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Highest Highest
    • FHIR Core (FHIR)
    • R5
    • Patient Administration
    • EndPoint
    • Hide

      A new property will be addded:

       

      Endpoint.payload.profile 0..* Canonical(StructureDefinition) | URI

      Short Display: "The profile that is expected at this endpoint."

      Description: "The profile that is expected at this endpoint, typically a FHIR profile describing the resources that are handled, or even simply which resource types -e.g. Vital Sign Observations or QuestionnaireResponse.
      A Uri may be used when a FHIR Structure Definition is not available/appropriate.

      e.g. CDA Template ID expressed as an OID (in the Uri)"

       

       

      Show
      A new property will be addded:   Endpoint.payload.profile 0..* Canonical(StructureDefinition) | URI Short Display: "The profile that is expected at this endpoint." Description : "The profile that is expected at this endpoint, typically a FHIR profile describing the resources that are handled, or even simply which resource types -e.g. Vital Sign Observations or QuestionnaireResponse. A Uri may be used when a FHIR Structure Definition is not available/appropriate. e.g. CDA Template ID expressed as an OID (in the Uri)"    
    • Brian Postlethwaite / Reinhard Egelkraut : 5-0-0
    • Enhancement
    • Compatible, substantive

    Description

      I have always understood that EndPoint.payloadType could hold the set of structureDefinition profile URI that the endpoint supports. This however is not indicated in FHIR core specification. The current definition seems to only provide a example valueSet made out of IHE defined FormatCodes. 

      Note that in IHE, we use the structureDefinition profile canonical URI as the FormatCode when that is appropriate. Such as in the case of IPS, we recommend that everywhere a formatCode is needed, the canonical URI for the IPS structureDefinition be used.

       

      Attachments

        Activity

          People

            Unassigned Unassigned
            john_moehrke John Moehrke
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: