briandiggle
commented
6 years ago Two main reasons:
1) The GP Connect FHIR API is designed for retrieving data from GP systems. So the GPC profiles reflect the primary care data model as that is where the data is sourced. Whereas updates will be published by all NHS sectors, using data not sourced from the primary care data model so the careconnect level profiles are a better fit. 2) The approach aligns with the transfer of care intitiatve which is publishing updates to gp systems from secondary care
The two data models are not massively different anyway - the GPC profiles are just constrained versions of the careconnect profiles.
The spec indicates CareConnect profiles rather than CareConnect-GPC for Patient, Org, etc. What are the reasons for this?