1. The focus of section 1.1 seems a little off. I think it spends too much time introducing IHE in general and not enough time describing the problem space that mCSD works in . I think it would be better to open by describing the complexities of the various use cases that mCSD solves and how mCSD is adaptable to that set of use cases (at a high level).

2. Both Facilities and Jurisdictions are defined in the whitepaper as a pairing of Organization and Location. It might be good to describe (at a high level) if/how one would differentiate between them in mCSD. In addition, are there situations where an arbitrary Organization+Location pair would define neither a Location nor a Jurisdiction?

3. "As
   such, the underlying Colleges will maintain the content and a Health Worker Registry would periodically
   refresh its content from these multiple underlying sources and execute necessary cross-referencing and deduplication
   workflows to support an interlinked registry relating WHICH workers provide WHAT SERVICES,
   WHERE."

A core part of this whitepaper seems to be about introducing the reader to the Location/Organization/Facility/Jurisdiction/Practitioner/HealthcareSerivce vocabulary. This text seems like a good place to use that terminology to help the reader link these concepts together.

4. I think the use case in 2.5 could be expanded upon a bit.

5. 2.8 is the only use case section that uses bullets. I suggest reworking this into more narrative style text like the others.

6. "Organizations can have more than hierarchy, but not Locations"

Is this intended to say that Organizations cannot have more than one Location, or that Locations cannot have more than one hierarchy, or something else?

7. "The following actors, transactions, and resources shall be used."

Use of the word "shall" here doesn't seem to fit the tone of the whitepaper. Maybe use "are" instead. I don't think we need normative language here, right?

8. Figure 46.4.1-1 in mCSD provides a nice visual of the relationship between the various concepts here. I think it would be good to work that into the whitepaper somewhere, possibly in 1.4?

in general include links to the profiles.ihe.net page, profiles.ihe.net/ITI, mCSD, and the HIE Whitepaper. Possibly point at the HIE-Whitepaper section on directories.

1.0

• don't bother introducing FHIR. Start with the problem you are writing about.
• the term "registry" needs to be introduced for the specific context you mean. There are many uses of the word registry that are well outside of mCSD scope
• isn't the term we use "directory"
• "This whitepaper will describe some common uses where mCSD can be used to discover organizational, services, and system details. The mCSD implementation guide can be used in various configurations, each suited for a different use-case. The variations will be discussed in the context of these common use-cases."
• WHAT does this mean? "support aggregate and patient-level indicator reporting" At what level does mCSD do patient-level details? This really concerns me.

that is as far as I read so far...