HL7CDA #905
Open
HL7CDA #905
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ote format to demonstrate this.
# Conflicts: # ResearchKit.xcodeproj/project.pbxproj # ResearchKit/Common/ORKResult.h # ResearchKit/Common/ORKResult.m # ResearchKit/ResearchKit.h
…pleted information - skip optional sections unless they have content.
…te section information to support it.
… CDA-compliant health document.
…HL7 CDA document type 'discharge summary'.
…ical Note document type.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Early HL7 CDA Support for ResearchKit
This PR adds some early support to produce HL7 CDA documents to ResearchKit applications.
The resulting documents can be easily imported to the Health app - so the user can store the results of their ResearchKit apps, print them, and share them with their physicians.
For researchers, the aim will be to work towards coding results with ResearchKit using SNOMED - so that results can be encapsulated into a document which is equally usable to patients, clinicians and researchers.
This PR focusses on trying to achieve a minimum working framework from which further development can occur.
A number of ORKResult types can generate by default results which are added into the result section of a document.
ORKSteps can insert text into any section of a document by using the hl7cda property, which can also be used to override any default results being produced by a step - there is an example of this in the Scales task in ORKTask. If you complete an ORKTask such as scales, for now ORKTest will produce the XML in debug - this can be copied and pasted into a text editor and passed to a validation tool, or you can send it to Health to upload into your own documents.
For now we are only creating the human-readable portions of the document - the coding will come later.
The framework allows us to generate any type of HL7 CDA document - for now only Continuity of Care Documents and Consultation Notes are defined.
Areas which need work (contributions welcomed!)