Hi,
On the call today there was a question on where to find CPs for the various IHE profiles we are using.
For the ITI profiles, you can find them here:
ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2015/CPs/3_FinalText/
and
ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2014/CPs/3_FinalText/
These are grouped according to the ballots for which they are approved, and so you may need to do some cross-referencing.
For example, as part of 2015, CSD has CP-800 as an approved change. The ballot which contained CP-800 can be found under Ballot 25 under:
ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2015/CPs/Ballots/
The 2014 Ballots are here:
ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2014/CPs/Ballots/
For changes affecting CSD Source Directories (e.g. RM, DHIS2, iHRIS) there are the following take a look at Ballot 23 for the CP-778, CP-781 and CP-782.
Hope this helps.
Cheers,
-carl
Hi All,
There was a request for a crib-sheet for the changes to CSD since last connect-a-thon. Here are the changes that will affect CSD source directories (e.g. the FR and the HWR):
- CP-800: For an entity such as a csd:facility, csd:organization or a csd:provider, we will no longer use the @oid attribute to capture the enterprise ID. Instead we will use the @entityID attribute. This @entityID attribute should be a UUID as expressed as an URN following RFC 4122. Although the intention is that the @entityID attribute has no semantic meaning, if you have existing internal identifiers that you wish to use to generate the @entityID, you may want to use a version 4 UUID which is generated from a md5 hash. You can also use a version 3 which is generated from a random number
- CP-782: This clarifies the use of the csd:otherName sub-elements of a csd:organization or a csd:facility to be an xs:string (there was a typo before and it was a data type for a human name). It also adds an optional xml:lang attribute. There were some other changes to the human name (used for csd:provider), but I don’t think DHIS2 or RM generated any csd:providers, so I will omit those changes here.
- CP-781: This fixes some typos in defining cardinalities on relating providers to organizations or facilities, and facilities to organizations in the XDS. I suspect everyone was doing this “correctly” already.
- CP-778: This fixes a typo replacing the @codingSchema attribute with @codingScheme, in particular for the csd:codedType element where things like the provider type or facility type are encoded.
If there are any questions on these, please feel free to reach out to me on Skype (litlfred_intra).
There were other changes to CSD, but these do not have an impact to source directories. If someone needs more info on these, please let me know.
Cheers,
-carl
···
On Jan 12, 2015, at 11:29 AM, Carl Leitner litlfred@gmail.com wrote:
Hi,
On the call today there was a question on where to find CPs for the various IHE profiles we are using.
For the ITI profiles, you can find them here:
ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2015/CPs/3_FinalText/
and
ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2014/CPs/3_FinalText/
These are grouped according to the ballots for which they are approved, and so you may need to do some cross-referencing.
For example, as part of 2015, CSD has CP-800 as an approved change. The ballot which contained CP-800 can be found under Ballot 25 under:
ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2015/CPs/Ballots/
The 2014 Ballots are here:
ftp://ftp.ihe.net/IT_Infrastructure/TF_Maintenance-2014/CPs/Ballots/
For changes affecting CSD Source Directories (e.g. RM, DHIS2, iHRIS) there are the following take a look at Ballot 23 for the CP-778, CP-781 and CP-782.
Hope this helps.
Cheers,
-carl
–
You received this message because you are subscribed to the Google Groups “OpenHIE Architecture” group.
To unsubscribe from this group and stop receiving emails from it, send an email to ohie-architecture+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.