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

There are now about 19 profiles based on Observation, consider consolidating to all purpose Observation with code specific rule pages

    XMLWordPrintableJSON

Details

    • Change Request
    • Status: Resolved - change required (View Workflow)
    • Medium
    • Resolution: Not Persuasive with Modification
    • US Core (FHIR)
    • 4.1.0
    • Cross-Group Projects
    • Blood Pressure Example
    • Home
    • 1.5
    • Hide

      It has been our experience that the readers prefer explicit profiles and don't like the indirection and abstraction like you are suggesting.    On the other hand , I agree that a the Observation profiles have proliferated we need to improve the organization and highlight the differences in a clear and simple manner.

       

      Proposal:

      1. Group and List profiles based on type instead of strictly alphabetically (see examples page for how it will look)
      2. Where applicable, for each Profile provide a link to a table that compares profiles across type.
      Show
      It has been our experience that the readers prefer explicit profiles and don't like the indirection and abstraction like you are suggesting.    On the other hand , I agree that a the Observation profiles have proliferated we need to improve the organization and highlight the differences in a clear and simple manner.   Proposal: Group and List profiles based on type instead of strictly alphabetically (see examples page for how it will look) Where applicable, for each Profile provide a link to a table that compares profiles across type.
    • Eric Haas/Isaac Vetter: 13-0-0
    • Clarification
    • Non-substantive

    Description

      With 19+ profiles all based on observation there would appear to be much duplication between them.

      Also, in my experience, this confuses people with thinking that a blood pressure observation profile and a BMI observation profile is an entirely different thing rather than 95% the same thing with a different code value in the resource.

      I suggest that the Observation Profile(s) be consolidated into a single profile where the structure, search params, etc. are all listed only one time. Put all the specific code rules in their own sub-(something).

      "If Observation.code = 1234 then SHALL populate X."

      "If Observation.code = 2345 then SHALL populate Y."

      Attachments

        Activity

          People

            Unassigned Unassigned
            dventon Daniel Venton
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: