- Lisa was concerned that the LOINC types would not be beneficial unless we provided specific guidance. <cda><code> = FHIR.type
- will try to reschedule when we have a larger group that includes Lisa and Swapna.
- General consensus at this point is that category is a broader concept that might be something such as "H&P" while type/code would be "Surgical H&P"
- 19732 - CDA on FHIR should be an IG that should the basis for C-CDA on FHIR. Wanted to consider the possibility of creating a CDA on FHIR profile. Discussed this back in December. Provide IG guidance. Might be useful in something that is not Realm specific, so could be used outside the US or for non-C-CDA projects.
- There is nothing in ClinicalDocument profile currently, which makes it somewhat useless.
- We may not be deciding that we are going to do it, but that we want to do it.
- There are several different organizations working on it in IHE.
- We could make a vote on if this is something we want to do.
- Maybe Rick would be interested in doing this.
- Sounds like the committee is feeling this is worthwhile.
- Talking to Graham and others.
- Would be worth seeing if the community feels there is interest.
- SDWG would like to do this but would like to see if there is community interest. Suggest talking to Grahame Grieve , Rick Geimer , and community sponsors.
- Trying to get more IG designers for FHIR. Maybe this would be a good starting point for training.
- 19710 - Tracker 17451 does not mention updating the targetReference to include Bundle. Suggest adding that via this issue.
- Will add Bundle to Composition.relatesTo.targetReference as an allowed resource type. Will add guidance on how to reference documents via both compositions and bundles.
- #55 - Persuasive with Mod
When Effective time is present it should have the right time and time zone offsets. - universally across rubric update EffectiveDate to EffectiveTime
#57 - If the Display Name is present then should throw an error if it doesn't match the vocabulary. If DisplayName isn't present then it shouldn't throw an error (deduct points)
Goals must be related to a specific health concern. In a Care Plan specific document, this may be true, but this may not be true universally.
- Goal usually has a related health concern entry and risk. Entry reference and then the reference can be used to reference many different things. There is nothing programmatic that prevents you from referencing. There is narrative that says it is entry concern act. There is nothing that prevents you from doing this. We should support the ability to relate this to a Health Concern Act.
- Proposal is to change the way it is related from Health Concern or Problem. The warning we can update to add the Problem stuff. In the context of the Care Plan, it is for Health Concern. In other types of documents, it will throw a Warning. Each goal must be related to a specific health concern in a Care Plan Document. In other types of documents it should be related to a Problem or Health Concern.
- Unknown User (george_dixon) If it is marked as part of the Care Plan they will pull that data.
- Gay Dolin In the Care Plan document, the rubric is correct. In the other documents, it is different.
- Care Plan requires the Health Concerns Section.
- In the warnings section, you must have a warning to the goals or health Concerns Section for other context for other Document Types.
- For the Care Plan documents, you need to indicate that the error was generated because you required a relationship to the Health Concern Section.
- "In a care plan document you must have a reference from a goal to the health concern." "For all other Document Types, when there is a GoalObservation entry it should have a reference from the goal to a health concern OR problem"
Copyright © Health Level Seven International ® ALL RIGHTS RESERVED. The reproduction of this material in any form is strictly forbidden without the written permission of the publisher.