Please enable JavaScript.

Coggle requires JavaScript to display documents.

GPC structured High Level View - Coggle Diagram

- - - - GPC Structured
      - GPC update record
      - GP2GP/PSS
      - PRM
      - SCR / HTML
      - EPS
      - GPC PFS
    - - Can be updatedby different projects to support new use cases
      - Centrally versioned (Different products may be on different versions
      - Changes authorised by INTEROPen SLT agreed process
      - Dealing with breaking changes?
      - Using packages to manage versions that can also be used to validate the message on the wire.
    - - Ownership?
      - Budget (could this fall under the IOPS standards budget?)
      - Stakeholder buy in? IOPS, GP IT Futures, INTEROPen, NHS E/I
      - Do we need to support parts of the data model that are only relevant to certain projects? e.g. may want to send Medicus entered in error via GP2GP.
      - Not sure of the best way to document this?
        Have a data model IG and an IG for each project using it.
    - - In both versions of FHIR.
        For R4 would be UK Core profiles on the wire but may have GPC profiles for validation.
      - Could be used to leverage change/encourage standardisation of GP systems (could be mandated that they support new fields)
      - Different products may consist of different sets of data items but all data items should be exported in a consistent format
      - Should only be one format to export individual clinical data items from a GP system.
      - How does the model fit into the wider context of NHS interop?
        Designed to work for different Architecture patterns/different clinical data patterns
      - Speaking a common language
        Save on dev, time, cost
        For
        NHS programmes, providers, consumers etc.