Granularity of FormatCode

The question is asked about the accuracy of the format format, especially if the definition of IHE of the FormatCode vocabulary has a smaller concept to understand the C-CDA HL7 code. Where is the FHIR menu included as FormatCodes ValueSet (updated to the current structure)?

IMPORTANT BACKGROUND: Elephant: Holding the IHE Health Information Exchange (HIE) Documents and Metadata on Health Care

FormatCode consists of technical format. This is another more accurate technical difference of representation. So it’s connected to the type of Maym.

FormatCode is not an alternative to class or type. It is possible to provide the same content in multiple formats. Integration of FHIR documents to XDS

The definition of IHE code format is usually one for each profile, since each C-CDA R2.1 is a unique format. The difference in this range seems to be a big difference, but at the technical level it is no different. This means that the IHR XPHR profile defines a unique set of restrictions on content content, where C-CDA R2.1 also defines a unique set of restrictions on content content.

This is the moment to explain that the so-called “profile” of IHE is usually published by HL7 as an “Implementation Guide”. Therefore, they are often like this.

Although XPHR has only one type (summary note in loop 34133-9), there are some unique use cases, each of which is unique in clinical “type” documents in C-CDA R2.1. This is a good example of why formatCode is not the same as “type”. The type expresses the type of clinical content in which a technical coding format is expressed.

Therefore FormatCode focuses on artistic discrimination as a pantomime type subtype and should be identified as necessary to understand the limits (or implementation guide).

HL7 can define a set of format formats of a secondary technical format format on C-CDA. They did not do it, I’m not there to explain why they did not. Theoretically, this should not be a problem. This only means that there is only one format at the technical level of coding, rather than one for each subform. I do not know how useful it is, but I’m glad to help the Commission understand the benefits.

I am the person who maintains this vocabulary. Not because it’s a party to create vocabulary, but just because I’m ready. If you have a problem with any of these sites or values, please let me know. I hear rumors that have problems, but as long as you refer to the problem with some details, I can not resolve it. This is true for FHIR where the request for change (CR) is sent.

Change health information: centralized, united or distributed.
Elefant: How to treat IHE documents for health information exchange (HIE)
Metadata for health care.

Leave a Reply

Your email address will not be published. Required fields are marked *