Skip to content
This repository has been archived by the owner on Oct 17, 2019. It is now read-only.

Fix initial specs. Single constraint and direct mapping. #13

Merged
merged 2 commits into from
Apr 18, 2018

Conversation

arscan
Copy link
Member

@arscan arscan commented Apr 17, 2018

Let's start with the single constraint, but I left the direct mapping as a case we should handle in the future.

Value: boolean

EntryElement: PatientDirectMapEntry
Description: "Maps directly to the Patient resource (no profile needed)"
0..1 ActiveFlag

Element: ActiveFlag
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we need to define this element twice? The ActiveFlag element from above should be usable in PatientDirectMapEntry too. If we do want both of these elements to exist (for the different description, for example), we should change ActiveFlag to a different name, because they're both in the shr.fhir namespace. Right now, only one of these (the second one) is showing up.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, good point, if that's how this works. I'm afk for a bit, so feel to commit a fix and merge, otherwise I'll do it when I get back.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(no need to have 2 different names for now, I just put in the directmap case so we don't forget about it)

@okeefm okeefm merged commit 5b3a146 into to_fhir Apr 18, 2018
@okeefm okeefm deleted the to_fhir_fix_specs branch April 18, 2018 16:40
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants