Skip to end of metadata
Go to start of metadata

This project scope statement has been replaced by the PSS in Jira with Project ID 1946




1a. Project Name

CHOICE Guideline for the use of a Fetal Resource

1b. Project ID

1746

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

1d. Is your Project Artifact being Reaffirmed or proceeding to Normative directly after being either Informative or STU?

1e. Today's Date

1f. Name of standard being reaffirmed

1g. Project Artifact Information

1h. ISO/IEC Standard to Adopt

1i. Does the standard include excerpted text from one or more ISO, IEC or ISO/IEC standards, but is not an identical or modified adoption?

1j. Unit of Measure

2a. Primary/Sponsor WG

Patient Care

2b. Co-Sponsor WG

Public Health

2c. Co-Sponsor Level of Involvement

Request formal content review prior to ballot

2d. Project Facilitator

Mike Padula, Michael Tan

2e. Other Interested Parties (and roles)

2f. Modeling Facilitator

Lilian Minne

2g. Publishing Facilitator

2h. Vocabulary Facilitator

Rob Hausam

2i. Domain Expert Representative

Mike Padula, Craig Newman

2j. Business Requirements Analyst

2k. Conformance Facilitator

2l. Other Facilitators

Shovan Roy, David Barnet, Ca

2m. Implementers

Children's Hospital of Philadelphia

3a. Project Scope

Goal of the project is to provide guidance in handling of fetal data. ( legal questions are excluded).
[another option (MP): Goal of the project is provide guidance in handling data relevant to the fetus in order to facilitate making those data available at the time of birth. Ultrasonographic and other imaging findings, pertinent genetic and labor
[What about (AG)]: not only at time of birth but also for youth health care (as preventive care) in where the child is monitored?
[AG] are the the data of a healthy fetus and/or child considered as within scope of the project? See powerpoint.

Attachments

3b. Project Need

A fetus is not considered as a patient, Some use body-site of the mother as an alternative, but this has drawbacks. Part of the project is to consider a simplified resource of a patient, which could evolve into a real patient, once the child is born.
[alternate option_MP: Information relevant to fetus....]
[AG] In the discussion in the expertgroup in the Netherlands the fetus is considered as a seperate entity. therefore the Patient can be used for the fetus. However, in different countries the week from which this is can be different. In the expertgroep 20 weeks of gestation is mentioned.

3c. Security Risk

No

3d. External Drivers

Babyconnect ( NL),

3e. Objectives/Deliverables and Target Dates

FHIR implementation guides, profiles

3f. Common Names / Keywords / Aliases:

Fetus model, body site, obstetrics

3g. Lineage

3h. Project Dependencies

3i. HL7-Managed Project Document Repository URL:

3j. Backwards Compatibility

No

3k. Additional Backwards Compatibility Information (if applicable)

3l. Using Current V3 Data Types?

3l. Reason for not using current V3 data types?

3m. External Vocabularies

3n. List of Vocabularies

3o. Earliest prior release and/or version to which the compatibility applies

4a. Products

FHIR Implementation Guide, FHIR Profiles, FHIR Resources, Guidance (e.g. Companion Guide, Cookbook, etc)

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4c. FHIR Profiles Version

4d. Please define your New Product Definition

4d. Please define your New Product Family

5a. Project Intent

White Paper

5a. White Paper Type

Balloted Informative

5a. Is the project adopting/endorsing an externally developed IG?

5a. Externally developed IG is to be (select one)

5a. Specify external organization

5a. Revising Current Standard Info

5b. Project Ballot Type

Informative

5c. Additional Ballot Info

5d. Joint Copyright

5e. I understand I must submit a Joint Copyright Letter of Agreement to the TSC in order for the PSS to receive TSC approval.

no

6a. External Project Collaboration

6b. Content Already Developed

6c. Content externally developed?

6d. List Developers of Externally Developed Content

6e. Is this a hosted (externally funded) project?

6f. Stakeholders

6f. Other Stakeholders

6g. Vendors

EHR, PHR, Health Care IT

6g. Other Vendors

6h. Providers

Clinical and Public Health Laboratories, Healthcare Institutions (hospitals, long term care, home care, mental health)

6h. Other Providers

6i. Realm

Universal

7d. US Realm Approval Date

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

7c. Co-Sponsor Approval Date

7c. Co-Sponsor 2 Approval Date

7c. Co-Sponsor 3 Approval Date

7c. Co-Sponsor 4 Approval Date

7c. Co-Sponsor 5 Approval Date

7c. Co-Sponsor 6 Approval Date

7c. Co-Sponsor 7 Approval Date

7c. Co-Sponsor 8 Approval Date

7c. Co-Sponsor 9 Approval Date

7c. Co-Sponsor 10 Approval Date

7e. CDA MG Approval Date

7f. FMG Approval Date

7g. V2 MG Approval Date

7h. Architecture Review Board Approval Date

7i. Steering Division Approval Date

7j. TSC Approval Date



Version

8

Modifier

Anneke Goossen-Baremans

Modify Date

Feb 22, 2022 11:53

1a. Project Name

CHOICE Guideline for the use of a Fetal Resource

1b. Project ID

1746

2a. Primary/Sponsor WG

Patient Care

2b. Co-Sponsor WG

Public Health

2c. Co-Sponsor Level of Involvement

Request formal content review prior to ballot

2d. Project Facilitator

Mike Padula, Michael Tan

2f. Modeling Facilitator

Lilian Minne

2h. Vocabulary Facilitator

Rob Hausam

2i. Domain Expert Representative

Mike Padula, Craig Newman

2l. Other Facilitators

Shovan Roy, David Barnet, Ca

2m. Implementers

Children's Hospital of Philadelphia

3a. Project Scope

Goal of the project is to provide guidance in handling of fetal data. ( legal questions are excluded).
[another option (MP): Goal of the project is provide guidance in handling data relevant to the fetus in order to facilitate making those data available at the time of birth. Ultrasonographic and other imaging findings, pertinent genetic and labor
[What about (AG)]: not only at time of birth but also for youth health care (as preventive care) in where the child is monitored?
[AG] are the the data of a healthy fetus and/or child considered as within scope of the project? See powerpoint.

3b. Project Need

A fetus is not considered as a patient, Some use body-site of the mother as an alternative, but this has drawbacks. Part of the project is to consider a simplified resource of a patient, which could evolve into a real patient, once the child is born.
[alternate option_MP: Information relevant to fetus....]
[AG] In the discussion in the expertgroup in the Netherlands the fetus is considered as a seperate entity. therefore the Patient can be used for the fetus. However, in different countries the week from which this is can be different. In the expertgroep 20 weeks of gestation is mentioned.

3c. Security Risk

No

3d. External Drivers

Babyconnect ( NL),

3e. Objectives/Deliverables and Target Dates

FHIR implementation guides, profiles

3f. Common Names / Keywords / Aliases:

Fetus model, body site, obstetrics

3j. Backwards Compatibility

No

4a. Products

FHIR Implementation Guide, FHIR Profiles, FHIR Resources, Guidance (e.g. Companion Guide, Cookbook, etc)

5a. Project Intent

White Paper

5a. White Paper Type

Balloted Informative

5b. Project Ballot Type

Informative

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Clinical and Public Health Laboratories, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

7

Modifier

Dave Hamill

Modify Date

Dec 15, 2021 17:47

1a. Project Name

CHOICE Guideline for the use of a Fetal Resource

1b. Project ID

1746

2a. Primary/Sponsor WG

Patient Care

2b. Co-Sponsor WG

Public Health

2c. Co-Sponsor Level of Involvement

Request formal content review prior to ballot

2d. Project Facilitator

Mike Padula, Michael Tan

2f. Modeling Facilitator

Lilian Minne

2h. Vocabulary Facilitator

Rob Hausam

2i. Domain Expert Representative

Mike Padula, Craig Newman

2l. Other Facilitators

Shovan Roy, David Barnet, Ca

2m. Implementers

Children's Hospital of Philadelphia

3a. Project Scope

Goal of the project is to provide guidance in handling of fetal data. ( legal questions are excluded).
[another option (MP): Goal of the project is provide guidance in handling data relevant to the fetus in order to facilitate making those data available at the time of birth. Ultrasonographic and other imaging findings, pertinent genetic and labor

3b. Project Need

A fetus is not considered as a patient, Some use body-site of the mother as an alternative, but this has drawbacks. Part of the project is to consider a simplified resource of a patient, which could evolve into a real patient, once the child is born.
[alternate option_MP: Information relevant to fetus....]

3c. Security Risk

No

3d. External Drivers

Babyconnect ( NL),

3e. Objectives/Deliverables and Target Dates

FHIR implementation guides, profiles

3f. Common Names / Keywords / Aliases:

Fetus model, body site, obstetrics

3j. Backwards Compatibility

No

4a. Products

FHIR Implementation Guide, FHIR Profiles, FHIR Resources, Guidance (e.g. Companion Guide, Cookbook, etc)

5a. Project Intent

White Paper

5a. White Paper Type

Balloted Informative

5b. Project Ballot Type

Informative

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Clinical and Public Health Laboratories, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

6

Modifier

Michael Tan

Modify Date

Nov 02, 2021 08:24

1a. Project Name

CHOICE Guideline for the use of a Fetal Resource

2a. Primary/Sponsor WG

Patient Care

2b. Co-Sponsor WG

Public Health

2c. Co-Sponsor Level of Involvement

Request formal content review prior to ballot

2d. Project Facilitator

Mike Padula, Michael Tan

2f. Modeling Facilitator

Lilian Minne

2h. Vocabulary Facilitator

Rob Hausam

2i. Domain Expert Representative

Mike Padula, Craig Newman

2l. Other Facilitators

Shovan Roy, David Barnet, Ca

2m. Implementers

Children's Hospital of Philadelphia

3a. Project Scope

Goal of the project is to provide guidance in handling of fetal data. ( legal questions are excluded).
[another option (MP): Goal of the project is provide guidance in handling data relevant to the fetus in order to facilitate making those data available at the time of birth. Ultrasonographic and other imaging findings, pertinent genetic and labor

3b. Project Need

A fetus is not considered as a patient, Some use body-site of the mother as an alternative, but this has drawbacks. Part of the project is to consider a simplified resource of a patient, which could evolve into a real patient, once the child is born.
[alternate option_MP: Information relevant to fetus....]

3c. Security Risk

No

3d. External Drivers

Babyconnect ( NL),

3e. Objectives/Deliverables and Target Dates

FHIR implementation guides, profiles

3f. Common Names / Keywords / Aliases:

Fetus model, body site, obstetrics

3j. Backwards Compatibility

No

4a. Products

FHIR Implementation Guide, FHIR Profiles, FHIR Resources, Guidance (e.g. Companion Guide, Cookbook, etc)

5a. Project Intent

White Paper

5a. White Paper Type

Balloted Informative

5b. Project Ballot Type

Informative

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Clinical and Public Health Laboratories, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

5

Modifier

Michael Padula

Modify Date

Oct 19, 2021 15:05

1a. Project Name

CHOICE Guideline for the use of a Fetal Resource

2a. Primary/Sponsor WG

Patient Care

2b. Co-Sponsor WG

Public Health

2c. Co-Sponsor Level of Involvement

Request formal content review prior to ballot

2d. Project Facilitator

Mike Padula, Michael Tan

2f. Modeling Facilitator

Lilian Minne

2h. Vocabulary Facilitator

Rob Hausam

2i. Domain Expert Representative

Mike Padula, Craig Newman

2l. Other Facilitators

Shovan Roy, David Barnet, Ca

2m. Implementers

Children's Hospital of Philadelphia

3a. Project Scope

Goal of the project is to provide guidance in handling of fetal data. ( legal questions are excluded).
[another option (MP): Goal of the project is provide guidance in handling data relevant to the fetus in order to facilitate making those data available at the time of birth. Ultrasonographic and other imaging findings, pertinent genetic and labor

3b. Project Need

A fetus is not considered as a patient, Some use body-site of the mother as an alternative, but this has drawbacks. Part of the project is to consider a simplified resource of a patient, which could evolve into a real patient, once the child is born.
[alternate option_MP: Information relevant to fetus....]

3c. Security Risk

No

3d. External Drivers

Babyconnect ( NL),

3e. Objectives/Deliverables and Target Dates

FHIR implementation guides, profiles

3f. Common Names / Keywords / Aliases:

Fetus model, body site, obstetrics

3j. Backwards Compatibility

No

4a. Products

FHIR Implementation Guide, FHIR Profiles, FHIR Resources, Guidance (e.g. Companion Guide, Cookbook, etc)

5b. Project Ballot Type

Informative

6g. Vendors

EHR, PHR, Health Care IT

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

4

Modifier

Michael Tan

Modify Date

Oct 19, 2021 12:00

1a. Project Name

CHOICE Guideline for the use of a Fetal Resource

2a. Primary/Sponsor WG

Patient Care

2b. Co-Sponsor WG

Public Health

2c. Co-Sponsor Level of Involvement

Request formal content review prior to ballot

2d. Project Facilitator

Mike Padula, Michael Tan

2f. Modeling Facilitator

Lilian Minne

2h. Vocabulary Facilitator

Rob Hausam

2i. Domain Expert Representative

Mike Padula, Craig Newman

2l. Other Facilitators

Shovan Roy, David Barnet, Ca

3a. Project Scope

Goal of the project is to provide guidance in handling of fetal data. ( legal questions are excluded).

3b. Project Need

A fetus is not considered as a patient, Some use body-site of the mother as an alternative, but this has drawbacks. Part of the project is to consider a simplified resource of a patient, which could evolve into a real patient, once the child is born.

3c. Security Risk

No

3d. External Drivers

Babyconnect ( NL),

3e. Objectives/Deliverables and Target Dates

FHIR implementation guides, profiles

3f. Common Names / Keywords / Aliases:

Fetus model, body site, obstetrics

3j. Backwards Compatibility

No

4a. Products

FHIR Implementation Guide, FHIR Profiles, FHIR Resources, Guidance (e.g. Companion Guide, Cookbook, etc)

5b. Project Ballot Type

Informative

6g. Vendors

EHR, PHR, Health Care IT

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

3

Modifier

Michael Tan

Modify Date

Oct 19, 2021 07:52

1a. Project Name

CHOICE Guideline for the use of a Fetal Resource

2a. Primary/Sponsor WG

Patient Care

2b. Co-Sponsor WG

Public Health

2c. Co-Sponsor Level of Involvement

Request formal content review prior to ballot

2d. Project Facilitator

Mike Padula, Michael Tan

2f. Modeling Facilitator

Lilian Minne

2h. Vocabulary Facilitator

Rob Hausam

2i. Domain Expert Representative

Mike Padula, Craig Newman

2l. Other Facilitators

Shovan Roy, David Barnet, C

3a. Project Scope

Goal of the project is to provide guidance in handling of fetal data.

3b. Project Need

A fetus is not considered as a patient, Some use body-site of the mother as an alternative, but this has drawbacks. Part of the project is to consider a simplified resource of a patient, which could evolve into a real patient, once the child is born.

3c. Security Risk

No

3d. External Drivers

Babyconnect ( NL),

3f. Common Names / Keywords / Aliases:

Fetus model, body site, obstetrics

3j. Backwards Compatibility

No

4a. Products

FHIR Implementation Guide, FHIR Profiles, FHIR Resources, Guidance (e.g. Companion Guide, Cookbook, etc)

5b. Project Ballot Type

Informative

6g. Vendors

EHR, PHR, Health Care IT

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

2

Modifier

Michael Tan

Modify Date

Oct 18, 2021 15:19

1a. Project Name

CHOICE Guideline for the use of a Fetal Resource

2a. Primary/Sponsor WG

Patient Care

2b. Co-Sponsor WG

Public Health

2d. Project Facilitator

Mike Padula, Michael Tan

2f. Modeling Facilitator

Lilian Minne

2h. Vocabulary Facilitator

Rob Hausam

2i. Domain Expert Representative

Mike Padula, Craig Newman

2l. Other Facilitators

Shovan Roy, David Barnet, C

3a. Project Scope

Goal of the project is to provide guidance in handling of fetal data.

3b. Project Need

A fetus is not considered as a patient, Some use body-site of the mother as an alternative, but this has drawbacks. Part of the project is to consider a simplified resource of a patient, which could evolve into a real patient, once the child is born.

3d. External Drivers

Babyconnect ( NL),

3f. Common Names / Keywords / Aliases:

Fetus model, body site, obstetrics

3j. Backwards Compatibility

No

4a. Products

FHIR Implementation Guide, FHIR Profiles, FHIR Resources, Guidance (e.g. Companion Guide, Cookbook, etc)

5b. Project Ballot Type

Informative

6g. Vendors

EHR, PHR, Health Care IT

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

Version

1

Modifier

Michael Tan

Modify Date

Oct 18, 2021 15:01

1a. Project Name

CHOICE Guideline for the use of a Fetal Resource

2a. Primary/Sponsor WG

Patient Care

2b. Co-Sponsor WG

Public Health

2d. Project Facilitator

Mike Padula, Michael Tan

2f. Modeling Facilitator

Lilian Minne

2h. Vocabulary Facilitator

Rob Hausam

2i. Domain Expert Representative

Mike Padula, Craig Newman

2l. Other Facilitators

Shovan Roy, David Barnet, C

3a. Project Scope

Goal of the project is to provide guidance in handling of fetal data.

3b. Project Need

A fetus is not considered as a patient, Some use body-site of the mother as an alternative, but this has drawbacks. Part of the project is to consider a simplified resource of a patient, which could evolve into a real patient, once the child is born.

3d. External Drivers

Babyconnect ( NL),

3j. Backwards Compatibility

No

4a. Products

FHIR Implementation Guide, FHIR Profiles, FHIR Resources, Guidance (e.g. Companion Guide, Cookbook, etc)