Feature ipa support #132
Feature ipa support #132
Conversation
# Conflicts: # input/fsh/DkCorePatient-Profile.fsh # input/fsh/DkCorePractioner-Profile.fsh # input/fsh/confidential.fsh
# Conflicts: # input/fsh/DkCorePatient.fsh
|
I would like to suggest that we do sort of like what the Finnish affilate has done (see https://hl7.fi/fhir/). Make DK Core compliant profilewise but keep IPA security aspects in its own separate IG like https://hl7.fi/fhir/finnish-smart/ @jacand how does that sound to you? |
|
That is also a good question for you @ovi-medcom & @christiangasser-lakeside 👆 |
Sounds good - with the possible exception of DkCoreObservation, which we may have to split in two? IPAObservations always have Patients as subjects, while we decided to keep DkCoreObservation open to other classes of subjects. -- and there is no multiple inheritance. We need to discuss how to move this one forward... |
|
we should probably follow this as well: HL7/fhir-ig-publisher#884 |
|
@jacand - I've introduced a new Observation profle - but maybe it isn't needed. That is still an open thing to consider. @tmsMedcom I think we should take up this PR for next available SIG meeting (and maybe retarget it to 3.3.0 branch). |
|
The IPA minimum requirements are very reasonable and we can leave out the SMART part and isolate that in its own IG ( early draft is here: https://build.fhir.org/ig/jkiddo/dk-smart/branches/master/index.html ) |
|
Which is comparable with the Finnish way |
# Conflicts: # input/fsh/DkCoreObservation.fsh
Original PR closed due to branch renaming. Continuing here from #76